Re: Re: commit control for an interactive web app, is this feasible

5250 isn't exactly like CGI, in most cases.  The Job
boundaries are the main difference.

But, I've written apps in 5250 written transactionally that
also could benifit from holding temporary records.  Using
data queues.  That way you have one server program that
reads info from a data queue, and does updates when
triggered.  Then there's always one job doing the db
updates, and CC is no problem.  Works for 5250, CGI, pretty
much anything.  

Brad

On Wed, 8 Aug 2001 11:35:59 -0400
 jon.paris@e400.com wrote:
> 
>  >> What did you have in mind as far an an app that would
> require CC and
> multiple steps along in the job?
> 
> As you say we are on different mental pages.  I am
> thinking of a simple
> Order Entry type scenario where (in 5250 land) I might
> create the Order
> Header, then from subsequent screens write the details,
> then ask for order
> confirmation and either commit or rollback the
> transactions.  Since my
> mental model works that way for 5250, I had seen no
> reason to use a
> different model for CGI.  I don't like messing with
> holding temporary
> transaction records unless I need to.
> 
> 
> _______________________________________________
> WEB400 mailing list
> WEB400@midrange.com
> http://lists.midrange.com/cgi-bin/listinfo/web400

Bradley V. Stone
BVS.Tools
www.bvstools.com