11:29 tiarra: 09:03:38 miyagawa: C shouldbe C</> if C is empty.
11:29 tiarra: 09:03:41 that reads oddly
11:29 tiarra: 09:03:54 does it mean that if both would be empty, PATH_INFO should be / instead?
11:29 tiarra: 09:05:22 miyagawa: the FAQ talks about IO::Handle->getlines, but the spec uses ->read
11:29 tiarra: 09:08:16 miyagawa: the spec says the body can be an arrayref of lines -- is it actually a requirement that each element of the arrayref end with \012? if so, it should be more explicit
Should it be documented that a working can() method is required for
the
IO::Handle like objects? Maybe any object without a working can()
method should
be considered broken, so it goes without saying... I just remember a
time when
CGI.pm had a broken can() method due to a use of AUTOLOAD.
One of my related frustations has been the various file upload
method APIs
out there. For example, CGI, CGI::Simple and Apache::Request all
handle this
slightly differently. Could you spell out how Plack helps with this?
I see that
that Plack provides Plack::Request::upload(), so perhaps the idea is
that frameworks
could re-use this rather than rolling their own.
miyagawa
commented
14 years ago
11:29 tiarra: 09:03:38 miyagawa: C shouldbe C</> if C is empty.
11:29 tiarra: 09:03:41 that reads oddly
11:29 tiarra: 09:03:54 does it mean that if both would be empty, PATH_INFO should be / instead?
11:29 tiarra: 09:05:22 miyagawa: the FAQ talks about IO::Handle->getlines, but the spec uses ->read
11:29 tiarra: 09:08:16 miyagawa: the spec says the body can be an arrayref of lines -- is it actually a requirement that each element of the arrayref end with \012? if so, it should be more explicit