Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Multi User Application - Guidelines?
Multi User Application - Guidelines? [message #873481] Fri, 18 May 2012 06:33 Go to next message
Tobias P. is currently offline Tobias P.
Messages: 43
Registered: April 2012
Member
Hello,

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 05:11 Go to previous message
Ralf Sternberg is currently offline Ralf Sternberg
Messages: 1290
Registered: July 2009
Senior Member

Hi,

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
RWT.getSettingStore().

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
[1] - a bit old, but the advices given there are still valid.

Regards,
Ralf

[1] http://eclipsesource.com/en/info/rcp-rap-single-sourcing-guideline/

--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Previous Topic:Single-sourcing with E4 apps?
Next Topic:Change default meta headers in M7
Goto Forum:
  


Current Time: Thu Aug 21 23:57:17 EDT 2014

Powered by FUDForum. Page generated in 0.01602 seconds