[WEB400] RE: commit control for an interactive web app, is this feasible

["Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>]

Being the "screwball" who started this mess of opinions-
here are a couple of cents of mine to throw into the pot too.

We do have a need to do the commit across screens
they select changes on a detail screen for items)
we show them then the result of those changes based upon class code
or other selection criteria, if that looks good overall, then they
can commit those to a change (this is multiple screens);
here-in was my philosophical question.
With a web app, that is not a persistent CGI, each time the user clicks
a key, you have a new job running, not just a new screen, thus was
the question of "how" and "does it work this way" came about for
creating the CGI programs that interact with the web user within
a named activation group so CC could be used (since it only ties to a job);
and thus with the replies on yes I can do this, and yes it does work,
even with the examples and the rest of the skill set that will follow
my footsteps, I see this as being too complicated a solution and
thus will be using work files date and time stamped to accommodate
a web user losing connection, closing the browser, jumping to another
site and forgetting to continue to do their SRP maintenance, line drops,
power outages, locked PC apps, and so on - this is not green screen,
the rules are slightly different (sort of yuk, and mostly exciting)-

We all have our opinions,
I thank all of you for yours, each opportunity will
have varying degrees of solutions and business reasons for those solutions;
I myself do not really like CC, but my opinion has nothing to do with
the requirements I have been asked to fulfill. (bummer)

I must be a control freak or something, I have looked over the CGIDEV2
and I must say, IMHO, I prefer seeing what, how, and the why that Brad had
explained in his book, but then again I like to know why and how my engine
works;
not just that it needs gas and oil.
-Mark




<snip>
No one has ever been able to show me a good reason to hold commitment
boundaries across screens. Assuming my premise, you would never need
persistence to use CC in a web environment either.

-Walden
<end snip>