How does jThinRich differ from browser/HTML based application development?
jThinRich has all the benefits of browser/HTML applications without the limitations. The client is still tightly coupled and controlled with the server end. For example, just like in the browser world, the client would still send a session token during each and every request to the server. The server still manages and tracks the session in all the same ways. The server is responsible for authenticating the user and issuing the initial session id, terminating the session after a inactivity timeout threshold is hit, and handling explicit user logout requests. Session management is very central to jThinRich. Somewhat similar to how cookies work in the browser world, jThinRich gives developers a simple session API for use on the client and server side. Details on how sessions are managed on the server side would still be an implementation detail for the server (db vs memory cache, load balancing etc). One can work with standard J2EE application servers and do this without restriction.
