It would be possible to do that, however you would need to make sure that this does not affect performance when sending messages around.
Shaping the RoomClient Objects to smaller Objects, that do only contain the information/params that are needed for the context of the method call they are used for is also a long term goal (for performance reasons). For example if you update any xyz property of the RoomClient currently the hole Client is send to all users, as only a single property might change (for example "isModerator" ). Potentially the same could be done to Whiteboard Objects. However in this case I think it would be needed to handle the actual task to store the WhiteBoard Object in a separated thread to make the sending of Whiteboard Object to all connected clients from a conference room fast. Sebastian 2011/9/28 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > is there any reason RoomClient objects are stored in hashtable? (according > to the code it is Entities and can be stored in DB) > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
