I understand that, in the normal processing of ADP pages, that the request contents have to be complete before the ADP starts processing. Is that right?
So, if we POST a large file to /example.adp, example.adp does _not_ run until the last byte of the file is POST'ed...right? And again, as far as I understand it, if we POST, instead, to a ns_register_proc'ed URL, (imagine, again, a large file), that proc starts running immediately (before the POST'ing is finished). You can read the contents which are coming in, as they are coming in. However, some routines that you can call will end up blocking your procedure from running until the contents are POST'ed - I think ns_form or something like that might do that. So - presuming those two understandings are correct what then happens if you do as follows: I have several ns_register_proc's that calls AdpParse - Ideally, I'd like to be able to 'stream' the contents and not force any blocking-until-end-of POST. The reason I do this is it makes development much easier for me - I get the ease-of-development of using ADP pages, and I get the power and control of Tcl pages... It may be something as easy as "dont use ns_form, and all will be well", but if so, I'd like to know that beforehand. Or it may be something like, "The second you call AdpParse, everything blocks until the request is finished posting..." Or maybe No requests run at all until the contents are finished being POST'ed or whatever. Adding to the excitement, I'm running an older version of AOLServer, but I'd be interested in hearing how this works on any of the versions. I presume this type of thing would be interested for anyone using AOLserver in a more infrastructure-oriented capacity, such as for a DAV server, or SOAP processor, or some-such. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
