Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spec/FAQ feedbacks #1

Closed
miyagawa opened this issue Sep 9, 2009 · 1 comment
Closed

spec/FAQ feedbacks #1

miyagawa opened this issue Sep 9, 2009 · 1 comment

Comments

@miyagawa
Copy link
Member

miyagawa commented Sep 9, 2009

11:29 tiarra: 09:03:38 miyagawa: C<PATH_INFO> shouldbe C</> if C<SCRIPT_NAME> 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
Copy link
Member Author

feedback merged.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant