On Feb 11, 2004, at 12:54 AM, Bruno Dumon wrote:
That's because the request is an object that lives only for the duration
of one request. Thus if you put something in a request attribute, it
only remains there for the current request.
OK — I figured that's what must be going on.
I'm new to Cocoon continuations and I had a bad think goin'. I thought "well, the request is part of the flow context, and a continuation ought to close over the entire context including the request". But of course not... it's not that there's one request that gets suspended and resumed, it's that you have one request that inaugurates the flow, and another request(s) that resume it. Yeah I get it :-)
The whole woody-flowscript integration is quite focussed on displaying one form at a time, so you're a bit on your own if you want to display multiple forms... (not that it's impossible, but you'll have to write some more code by your own.
Right, I kind of saw that coming :-) I figure all the pieces are there in woody2.js, I'll just have to put them together differently.
thx-a-lot, ~ml
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
