Hello Daniel,
Am 01.01.2025 um 08:55 schrieb Daniel Gross <daniel@xxxxxxxx>:
So IMHO it about time to create a new paradigm - maybe a new protocol - which offers sessions/transaction control. So that when the connection is interrupted, the session drops and open transactions are automatically rolled back.
You have a good point. Sadly, history proves that good solutions (needing more effort in the first time to be rolled out) often are hampered by the "good enough" approach which unfolds over time and again and again leads to messy "solutions": A stack of not really fitting tools for the job being forcefully bent into "fits a bit better", and added kludges to work around the rest of remaining issues.
The result is what we have now: At the base connectionless http requests stacked to the website which involves local logic on the client to deal with all the intermediate stuff for presenting data to the user. Just as you described in a message earlier.
But as long as "it just works" is the chosen way of short-term fixes to a greater issue, adoption of a well architected solution from scratch will be slow to not-happen. Sad.
:wq! PoC
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.
midrange.com
