× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: commit control for an interactive web app, is this feasible
  • From: jon.paris@xxxxxxxx
  • Date: Tue, 7 Aug 2001 12:02:22 -0400


I've not tried commitment control within a CGI program but it should work
as long as you are using persistent CGI.  The only working example programs
that use persistence that I am aware of are part of the CGIDEV2 package and
can be found at www.easy400.ibm.it.  Brad Stone may have an example on his
site (www.bvstools.com) but I didn't see one the last time I visited.

Most folks seem to stay away from persistent CGI because dealing with the
session time-out issues causes as much if not more work than maintaining
your own persistence information.  However, in your case if the session
dies I guess you just want to roll back as you would if the 5250 was
unplugged so it probably is worth considering.  Without persistence you
will have to do it all yourself unless you spawn a "batch" job for each
user that sits on the end of a dataqueue and do all of your IO stuff there.
Probably not worth the effort.

+---
| This is the WEB400 Mailing List!
| To submit a new message, send your mail to WEB400@midrange.com.
| To subscribe to this list send email to WEB400-SUB@midrange.com.
| To unsubscribe from this list send email to WEB400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.