"Grace S. Aguilar" wrote: > > On the other hand, one of the major issues is that, the system will be > ran on a disk-less environment and that, multiple concurrent access is > expected (issue on multi-threading). >
It's a little unclear what you're trying to do, so it's impossible to (intelligently) answer your questions. Is the client or the server the thing running on a diskless workstation? If it's the client, why do you care about "multiple concurrent access"? That's up to the server (and it's already taken care of for the most part if you're using servlets) What exactly do you mean by "diskless workstation"? The kind I'm familiar with boots up over a LAN and has over-the-network swap. It sounds like you're talking about someting different? What do you mean? How will the client and server be connected? Over a LAN, or a WAN? It makes a big difference. If it's a WAN, that will probably be your single biggest user-perceived performance problem, and it has nothing to do with Swing or threading. Why do you keep asking about multithreading? Are you talking about starting a new thread for each client request on the server? Servlets takes care of that for you. If you're talking about mulithreading on the client, why? What makes you think it would help? > Would appreciate your comments specially on performance > issues. Thanks again! > Again, you haven't given enough information to answer your question. You can only discuss performance in the context of some sort of system architecture, and even then you have to be specific. What do you mean by "performance"? Are you talking about the client or the server? If the client, are you talking about how fast it starts up (you seem concerned about download times), or how fast the client responds to the user during local input, or how fast the server responds to the client when some data is submitted? Or how fast the user _thinks_ it is responding (user-perceived performance is only indirectly related to actual software/hardware/network performance) As far as Swing goes, I just saw a demo (on Windows) of a Swing application that ran as fast as a native application. Before believing the standard reflexive "Oh, Swing is slow" response, you need to test for yourself. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
