||unity-dev|| Diferences between invokeOnRomm and setClientAttribute

Discussion list for Unity developers. unity-dev at moock.org
Fri Feb 16 06:42:25 CST 2007


Hi!

We have made our first multiplayer game! yeap!!! :-) 

All it's ok, but in some cases we think we are not using Unity correctly. We know Unity is based on a MVC Pattern, but in some situations we don't see clearly which is the model, the view or the controler (almost always in the client part). The most problematic to understand for us is the mission of the class that extends Uclient.

What are the differences between invokeOnRoom and setClientAttribute? What are the situations to use one or another? What are the criterions to select invokeOnRoom or setClientAttribute? 

An example:
I want to send a message to all clients connected. Each client have to detect this message, and processing it in his view (like a graphic chat). I think this example requires invokeOnRoom, but is possible to do it with setClientAttribute... 

Thanks,

marcos
www.q-interactiva.com


More information about the unity-dev mailing list