Originally posted by Philip Pomario:
Guys, the system requirements states that response time should be very fast and that a "graphical user interface" must be available to a special type of user.
The main question is: What is your understanding of a "graphical user interface"? Is it obligatory to be a standalone fat client (such as Java Swing apps)? Or could it be a webapp running on a very small container (such as Jetty)?
Your comments are much appreciated.
Originally posted by Ben Two:
Hi Philip Pomario
In a Fat Client, like a Swing application, the dataset can be cached in client JVM, that means most of the time it does not need a communication to server, only load the initial data when the application starts and then periodly refresh the data, and finally connect to server when transaction commit.In this case the response time will be much more faster than a web application like JSP or Servlet, because theoretically we only need twice connection to the server, start up and commit.
The overall mission is to change the world. When you've done that, then you can read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton