[x3d-public] Question about MU and Network Sensor

[GL]

Christoph,

Let's say for example that you have an avatar wearing a hat and carrying a bag. That avatar opens a car door, gets in and drives away.

Are you suggesting that the avatar, the hat, the bag, the car door and the car itself should all have a separate NS within and make each their own connection to the server? It is feasible, but unless I am missing something from this reasoning, my take on it would be that the server would get overloaded rather quickly, resulting from all of the extra connections. So in other words, instead of being able to handle say 50 avatars per machine, now we'd have only 10 (in this example), since each model would have to synchronize via their own connection. Also, network latency could cause the hat to fall behind or the car door to get ahead of the car and everything. 

Like I've mentioned before, I could see something this working somewhat better with Java3D (though I haven't touched it in years), but with X3D it brings up questions to my mind. So to answer your question, IMO it is better to have fewer connections and pack as much info into them as possible. But assuming that you'd want to do it anyway, the models would still work and interact with the scene as specified (however we're getting into other considerations here that exceed the context of this post).  

GL

From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Christoph Valentin
Sent: Saturday, April 20, 2019 12:26 PM
To: x3d-publicweb3d.org
Subject: [x3d-public] Question about MU and Network Sensor

Dear all,
 
Am trying to figure out one detail about the highly discussed "Network Sensor".
 
Have now explained the "operational paradigm" of the network sensor, as I think to understand, at our SP-ARK WIKI:
 
https://github.com/christoph-v/spark/wiki/Operational-Paradigm
 
If you follow that link, you will find I am trying to use my own words in order to describe the well-known. This is not only due to the fact that I have got a fatal tendence to invent the wheel another time and another time, it it also due to Copyright considerations.
 
If you follow the link, then you will find my impression the interface of the Network Sensor is twofold.
 
First there is the what-I-call CNSI (Common Network Sensor Interface).
 
Second there is the what-I-call SNSI (Specific Network Sensor Interface).
 
Now getting to the point: is it acceptable to require the SNSI MUST remain WITHIN the model? Is it allowed to have it affecting the "master scene"?
 
I think this is an important question, otherwise I wouldn't bother you.
 
All the best
 
Christoph
 
P.S.: Currently the WIKI has got only two pages, the home page is https://github.com/christoph-v/spark/wiki