[Fiware-miwi] App architecture sketch

[Torsten Spieldenner]

Hello,

> I don't understand what these two separate members are, the components list and the viewElement. What would the XML3D representation entail there?
>
> In the EC model the idea is that everything is in the components, the structure is like this:
>
> entity =
> {
> 	id,
> 	components: { component1, component2, .... component_n }
> }
> And information about how visible objects display is in the respective components: for example the scene node position in EC_Placeable and the geometry for meshes in EC_Mesh etc.

That's actually how we represent the entity now as well. The previous 
design with the separate XML3D element was a first idea to take 
computational work for creating an XML3D scene graph out of the 
components from the client. My idea here was to apply transformations 
that are described in the components on server side, and then transmit 
the resulting XML3D representation together with the actual entity. 
However, in the meantime, we decided against this approach and 
represented the entities just as you pointed out above.

I'm currently still doing some changes to the code that performs the 
client server communication. As soon as I am finished, I will put a 
rough architecture description as well as a description of how 
synchronisation of our system works into to FI-Ware Wiki. I try to get 
this done later today, in worst case tomorrow.

~ Torsten