Re^2: Are all .cgi helper modules unfit for http methods common in REST?

Have you submitted a bug report?

No account. And who solves these bugs anyway? ;)

dedicated webserver .. mod_perl

Already in the pipeline (as everything else turned out to be a wall). But does that mean there is no equivalent for the CGI interface?
Further, running a dedicated HTTP webserver for us perlheads means building something around HTTP::Daemon (which for me seems to be unstable, see this node or Net::Server with a completely unusable ::HTTP implementation.

Second, mostly you'll end up describing your requests as HTTP::Request objects, which is great, but these aren't procedural as well. So you'll end up waiting for a HTTP::Request object to complete, with a 2GB content variable - and you've got no access to it while it arrives. No buffered reading, no partial XML parsing possible...

Comment on Re^2: Are all .cgi helper modules unfit for http methods common in REST?

Replies are listed 'Best First'.
Re^3: Are all .cgi helper modules unfit for http methods common in REST? by Anonymous Monk on Aug 12, 2010 at 20:18 UTC
No account. And who solves these bugs anyway? ;) You claim there is a bug, but you won't submit a bug report? But does that mean there is no equivalent for the CGI interface? No, it doesn't mean that, that would be jumping to conclusions. ...see this node ...No buffered reading.... Not very authoritative ... see Re^2: POST'ing a large File with LWP::UserAgent for one example, if LWP::UserAgent can use callbacks to chunk file uploads and downloads, so can you	[reply]
Re^4: Are all .cgi helper modules unfit for http methods common in REST? by isync (Hermit) on Aug 12, 2010 at 20:24 UTC
Okay, more like a feature-request..	[reply]