+-------[ Tarek Ziad? ]---------------------- | Andrew Milton wrote: | | >+-------[ Tarek Ziad? ]---------------------- | >| Andrew Milton wrote: | >| | >| >The actual submission is to a small CGI that handles updating the status inside | >| >Zope via XMLRPC (you could also update a response file that the product could | >| >check as well, but, that's just more files that have to be written to and | >| >removed), when it's complete it passes in the location of the file(s) to the | >| >Zope Product so it can process them further (by spawning a worker thread, so | >| >you don't stop Zope from responding to requests). | >| > | >| > | >| oh k. i am trying to add this directly to the publisher, by providing | >| a set of api and keeping running request state. | > | >Yeah ugly. I don't think distributing a Product that monkey-patches ZPublisher | >would be all that warmly received d8) | | I was not talking about doing a monkey patch there, but add a feature | within the publisher.