Hi Andun, that sounds great. You don't need to keep too much attention on the previous XML format (so called WML format). This format is basically the output when you serialize the whiteboard object to XML using the XStream library.
Just to clarify: With "saving the whiteboar on server side" I don't mean when the user clicks on "saving a whiteboard", what I mean is for instance the use-case: You simply draw objects on the whiteboard, and all users leave the conference room, and return/re-enter to the room => The objects should be still on the whiteboards. Or in other words: The current state of the whiteboard has to be saved somewhere on the server, so all users that enter the conference room sync against the server side whiteboard "cache". There are a number of lessons learnt from past implementation of this "cache": - We want to cluster OpenMeetings later to scale a conference room, best would be even to cluster single rooms accross multiple server instances. So all servers need to be able to access this "cache" - Writing the cache to a file is not so good in terms of performance. File operations usually take quite long (open/write/read file). Also concurrent access to the File system is an issue. Same issues but not as extrem for storing it in the database. This whiteboard cache is basically really a "cache", and we want quick access to it. So really the memory is the best place. I think your current approach using Java Objects in a HashMap is the best for now. We might need to discuss at a later stage how we can make this cache available between servers in a clustered environment. Storing the objects in Ehcache might be one option. Ehcache has build in mechanisms for scaling + provides the necessary performance (and is Apache Licensed). Thanks for that input Andun! Sebastian 2013/8/4 Andun Sameera <[email protected]> > Hi Sebastian, > > In the current implementation, I have implemented most of the client side > drawing functionality and working on the missing things. > > In the server side all the whiteboard elements are represented as JAVA > objects and kept in a HashMap. Also to long term persistance we are > palnning to save the whiteboard content to the previously used XML format > with a mapping to new JSON format. > > Thanks! > > > On Sun, Aug 4, 2013 at 10:27 AM, [email protected] < > [email protected]> wrote: > >> Hi there, >> >> I see you are quite busy in the implementation of the HTML5 whiteboard :) >> >> I would like to touch bases to see what are the plans in terms of server >> side integration. >> Or is that currently not yet on the roadmap? >> >> Question would be where and how those whiteboards are stored on server >> side. >> >> Thanks! >> Sebastian >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > Regards > Andun S.L. Gunawardana > Undergraduate > Department of Computer Science And Engineering > University of Moratuwa > Sri Lanka > > Blog - http://www.insightforfuture.blogspot.com/ > LinkedIn - http://www.linkedin.com/pub/andun-s-l-gunawardana/34/646/703 > Twitter -http://twitter.com/AndunSLG > > > > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
