Ian Sparks [mailto:Ian.Sparks@...] wrote:
> Paul Boddie [mailto:paul.boddie@...] wrote :
> >The big question, however, is: what happens to all those threads if =
> >average user never fills in the first registration page? ;-)
> I believe the ATCT acts as a virtual machine able to suspend threads =
> disk until they need to be re-activated. You might get a few "thread
> files" lying around on disk but they don't take up any other resource
> while they're inactive.
And of course you can periodically delete those thread files, I suppose. =
few years ago, people might have been worried about the resource demands
that this approach might take, but in this age of laptops with 0.5GB =
RAM and 80GB disks, I would guess that it isn't a problem any more. ;-)
> >After various local DNS issues, I managed to get a page which looked =
> >it were some kind of proxy error.
> Yes, I've been getting that too though it looks like its back up now. =
> not do a search on " sendPageAndWait("/registration1.jsp", null);" in
> google. The only cached result is Alex's page.
I might well take a look. Personally, I believe that a better exposed =
machine is really the way to go in Web applications. It may initially be
more succinct to write "workflows" as straight code, but in the large =
I'd want tools to be able to manipulate the different sequences of =
and the conditions that are tested to send users between those screens.