Bad idea ... Service should be stateless ! State should be store in session scope. Guice or Spring could be a great help (but with different approach). HIH
On Wed, Jun 23, 2010 at 9:58 PM, Ralf B <[email protected]> wrote: > I have a service that instantiates and keeps state (variables in the > back end that is controlled by the service) until the user logs out. > What happens exactly when two users access my GWT service; will there > be one service instance for each user or will one be shared between > them? I try to figure out if my service is actually multi-user or > not... > > Ralf > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- "Computers are useless. They can only give you answers." - Pablo Picasso - -- 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.
