|Multi User Application - Guidelines? [message #873481]
||Fri, 18 May 2012 10:33
| Tobias P.
Registered: April 2012
we are planning to develop a multi user application in the near future. Multi user means, you can login and every unique user has its own persistent workspace.
As far as i know, something like that is not implemented yet.
Are there best practices,guidelines or something like that available?
|Re: Multi User Application - Guidelines? [message #875174 is a reply to message #873481]
||Tue, 22 May 2012 09:11
|| Ralf Sternberg
Registered: July 2009
Just to avoid misunderstandings, let me just point out that every RAP
application is, of course, a multi-user application. RAP also supports
user-specific, persistent settings using the setting store, see
If I understand correctly, you plan to implement an Eclipse workspace in
a RAP application, right? To do so, you will have to implement at least
the core.resources plug-in for RAP. To my knowledge, this hasn't been
done yet. So, apart from the usual advices (care with static fields,
singletons, etc.) there are no specific guidelines for this task. If you
haven't done yet, you might want to check out our single sourcing guide
 - a bit old, but the advices given there are still valid.
Professional services for RAP and RCP?
Powered by FUDForum
. Page generated in 0.01650 seconds