So far the only issue visible to the end user while using multiple OM servers was: room user count is wrong.
This is because we have implemented clustering with "manual balancing" i.e. Each room has its own server and while entering room user gets redirected to the server current room belongs. I guess I'll add RoomClient storing in DB in customer's SVN, hopefully it will not clow down everything. On Mon, Jun 25, 2012 at 1:56 PM, [email protected] < [email protected]> wrote: > Session data is usually never stored to the database. > For example with sync events, you need to be very fast in sending those > events to every participant. > So for example if you need to update a database object every time you send > a sync event you slow down that process. > I could imagine that having the RoomClient in the database will be not so > much a performance problem then other session objects. I guess we have done > that just because of consistency. > But for example have the whiteboard-session-objects in the database will > be not possible because of performance. > When you do the clustering will you need to store _all_ session related > objects to database or is it only about the RoomClient? > > Sebastian > > > 2012/6/25 Maxim Solodovnik <[email protected]> > >> Hello Sebastian, >> >> Can you remember what was wrong with storing RoomClient in DB? (I do >> remember you have removed this object from the DB) >> Right now I'm implementing clustering support for one of our customers >> and the only issue remaining: The number of users in room is not updated on >> different servers since RoomClient is stored in in-memory hashtable. >> >> Thanks in advance >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.openmeetings.de > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax
