|Preferences and states per User [message #1233881]
||Mon, 20 January 2014 13:31
| Daniel Branco
Registered: January 2014
I'm trying to understand the preferences and user states in Scout.
As far as we have investigate, Scout seems to use Eclipse Preference storage mechanism normally.
The situation is the following, having the MiniCRM example opening the 2 instances of application through web (RAP), if one anonymous client make changes in the tables the other one after refreshing will see those changes.
So we decide to implement a Basic Security Filter in the RAP and Server config.ini, login with different accounts and remain the same problem, the preference file was overwritten using the same keys, so both users were seeing the changes after refreshing.
My question is how can I save different changes in the UI where only that logged user can see it? I mean a unique preference key per user login.
Furthermore, we were testing the application in SWT to understand if the preference were saved by the client or by the server, and effectively this is done in client, but our interest is to have the preferences centralized in the server and read those preferences no matter where the user logged is, is there any mechanism for this or a hint to do it?
Powered by FUDForum
. Page generated in 0.02047 seconds