This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
"No, neither of those. If you want to deploy an application to many users, even if they are all in the same office, you should consider using JNLP (Java Web Start) to do that.
In any case, whether they run the application via JNLP or from a mapped drive (was that what you meant?), the application will be running in a separate JVM on each separate user's computer. "
In other words; the application is stored once; and the virtual machine creates as many processes as users use the application; and the application will run in each computer's Java virtual machine? I gues I am trying to find out whether I have to include some code so that the application can by run many users at the same time or whether the virtual machine will take care of that. Is the process forked by the virtual machine?
"Support for multiple users in Enterprise Java applications is provided by the application server in the form of multi-threading. Each user-request is mapped to a thread, which takes care of responding to the user-request. The application developer writes his application as if only one user was using it (with a sprinkle of thread safety). The server takes care of the rest by running your code in multiple threads and mapping user-requests to threads. What works for one user suddenly also works for thousands of users. This is a great advantage: Not much to do for the developer to accommodate a large number of users."
If this is the way it works. Could you please point to any readings that deak with the code to add a sprinkle of thread safety as stated above?