Well you could use basic authentication by setting username and
password inside the header for every request you make. If you want to
have a login page you can either redirect to the spring security page
(which should redirect you right back) or you can create your own
login page/dialog. The
Well there is a browser cache already. Once you've configured your
server to send out some cache related headers you get a client-side
cache with no further additional work.
On Thu, Sep 16, 2010 at 2:36 PM, Marcin Zawadzki
marcin.zawad...@gmail.com wrote:
Take a look at this, might help
I've been using multiple EventBus instances together with Gin/Guice
and named annotations. So for example each view that needs to
communicate in some way with my REST server is attached to the @Server
HandlerManager. That way each component can have multiple
communication channels open and it is
g:Hyperlink targetHistoryToken=YOUR_TOKEN_HERE /
clicking this link will add a new history item with the given token
and will fire a new ValueChangeEvent.
On Thu, Apr 22, 2010 at 10:44 AM, raj raj.cowbo...@gmail.com wrote:
Hi !
I'm working gwt2.0 UIBinder. I tried to maintain history in my
