Re: Approaches to develop a stateful application

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.

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.

On Mar 23, 2:44 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On 22 mar, 23:13, stsch <stsc...@schliwinski.de> wrote:
>
>
>
> > I have just started with GWT. What are the approaches to develop a
> > stateful GWT application? Could any of the experts please summarize
> > this a bit for a beginner and maybe point me/us to some reference
> > material?
>
> Keep your server stateless and store all state information in the
> client (you can use static fields for example).
>
> I find it much easier to "think stateless" on the server side (aside
> from "ReST" arguments), but of course YMMV and you're still free to
> choose HttpSession (or other session mechanism, if you don't use Java
> server-side) if you prefer...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to Google-Web-Toolkit+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---