Hi fellow members,

I have been following examples found on the web to build my web
application with RPC mechanism.

My web application has quite a few services. By right, each service
should have its own class files on both client and server side. But
this way will result in a lot of class files, quite troublesome.

So I'm grouping all the services into one "union" set of class files.
It works for single-user usage, soon I have to test on multi-user
environment and wonder if problem can arise.

Say if users using different services concurrently and yet I have
grouped the services together, will my web application crash (it can't
tell which service for whom) ? Or I'm worrying too much as there will
be individual instance of the class files for each user?

Just want to get this right before I continue developing~ Thanks in
advance :)

Regards,
style.x7

--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to