On 23 mar, 16:44, Magius <[email protected]> wrote:
> That's true, the easiest way is to store all the posiblle information
> in the client side. And in this way you application is more scalable.
> Anyway, there are some information that I have to store in the server.
> I have often 1 or 2 servlets for PDF/XLS/JPG generation that need to
> shared some basic information with GWT.
I do too, but I made them stateless nevertheless (although I concede
that it's not always easy and in those cases, a small bit of state on
the server side is worth it wrt time/money constraints).
(see below however)
> And a flag to know if the user is logged or not. Otherwise you have to
> send always the user and password (in a non readable way, etc). And if
> you use several HTML in the same app or SSO you'll need to.
This does not mean your server has to be stateful. Authenticating
using a "ticket" associated with a given user (as the result of
"calling a resource" with the appropriate credentials), that expires
after a few minutes of "inactivities" does not imply using sessions.
I am using such a thing, and the tickets are stored somewhere in the
database (that's not something we've developed, it comes with the
product we're building upon). The same ticket can be used with
different "sessions" if you are capable of passing it to the server
(we have some cases where we pass it in the query string; looks awful,
isn't "restful" at all, but it just works and saves us from some re-
authentication needs; specifically, we use this in the URLs of our
FormPanel when we do uploads, and in the WebDAV URLs we give to MS
Office --through an ActiveX, in the "ie6" permutation only-- to enable
online editing of office documents). We do use the "ticket" in a
cookie too, but that doesn't imply an HttpSession in the server either.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
