Henrik,

Thanks for the reply. Regarding "stateful" vs. "stateless" interfaces...
Wouldn't it be more useful to say that the vast majority of business
applications require "state" to be managed? Isn't it more a matter of "how"
that is done? Whether state is managed in the client, or on the server?
Whether individual user "state" is maintained in separate JOBs? Or, in the
event of a single job servicing multiple concurrent clients, state being
saved and restored within the request-response cycle?

Regarding database state, I find that most applications maintain persistent
connections for individual clients, especially the more functional the
application.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.