Kemin Zhou <[EMAIL PROTECTED]> writes: > Joe Schaefer wrote:
[...] > >Despite my past grumblings to the contrary, I've added support for > >tempname to httpd-apreq-2's current-cvs. [...] > Thanks for the help. The tempname is not available in mp2. You misunderstood me. When I read your article, I thought you gave sufficient reasons as to why apreq2 should support tempname, so I wrote an implementation and committed it *right then* to cvs. Prior to your article tempname() was unimplemented in apreq2 (in fact it was *removed* from the documentation not more than a day or two prior to your post). [...] > I don't know how this is implemented. I used to write my own file > upload method. Some of my web applications still use these methods. > It is very simple. That's all fine and dandy, but apreq2 is operating under more stringent requirements. There is a coercive effect when you implement your own data parser: unless everyone else adopts your implementation, somebody inevitably gets left out of the loop. apreq2 imposes no adoption requirements on other modules. For instance you can implement an auth handler with apreq2 that parses the post data, which then decides to accept the request and hand it off to a cgi script. The cgi script will still have the full POST data available for it to use/parse. Or you can write a content handler that uses apreq2 which parses the post data and then does an internal redirect to the proxy handler. The proxied server will still see the original POST data, without any extra code by the content-handler author. [...] > Put more thoughts into uploads could benefit the future. Thanks, we'll try. In the meantime I've rolled another snapshot of current-cvs that you're very welcome to try http://cvs.apache.org/~joes/libapreq2-2.04-dev.tar.gz -- Joe Schaefer -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
