Bertrand Mansion wrote:
On Sat, Nov 7, 2009 at 12:32 PM, Jacob Jay <[email protected]> wrote:
My point was that I think it would be handy if wsapi could allow
different request parsers. For example, I don't think ?foo[bar]=1
would be converted to a table. What about ?foo.bar=1, ?foo[] = 1 or
even ?foo[1]=1
I'd like to have a way to change the default behaviour. It might
already be possible though, I didn't check...
I believe a non-standard parsing behaviour should be handled by an
application itself (i.e. in the application developers code) not WSAPI which
is providing common ground between the HTTP server and language. The HTTP
standard behaviours are ?name=value&etc (table) or ?value+value+value+etc
(array) and WSAPI providing a table for these is helpful.
Do you have a link to HTTP RFC or something describing this standard way ?
Well, the name=value&etc is part of the HTML spec (not HTTP) here:
http://www.w3.org/MarkUp/html-spec/html-spec_toc.html#SEC8.2.1
Is is called "application/x-www-form-urlencoded" encoding.
_______________________________________________
Kepler-Project mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
