According to ServiceLayerCache, the cache is implemented as a static
variable, so locator services and methods may be cached for all users. Your
locators and service instances should therefore not keep any user-specific
info, but rather obtain it in each method through a call to
getLocalThreadReque
what if the decryption stuff is also user/session-specific ?
i read that rf caches locator-instances, will it be safe if i use
getLocalTheadRequest() at locator-methods to get the session-stuffs for
decrypting the data ?
thanx
On Tue, Feb 8, 2011 at 6:13 PM, David Chandler wrote:
> Hi khiem,
> A
Hi khiem,
As of 2.1.1, you can replace static findEntity() methods using a Locator and
ServiceLocator. Updated RF docs are available at
http://code.google.com/webtoolkit/doc/trunk/DevGuideRequestFactory.html. A
locator method implemented in a separate Locator class could decrypt the
entity and retr
hi,
i'm using Proxy-Entity with Locator for a gwt-app & got into problems
concerning this issue
http://code.google.com/p/google-web-toolkit/issues/detail?id=5724
eg. i have several users, which retrieve data from DB, the data will be
retrieve from db & decrypted before delivering back to user,
