* Thus wrote Sara Golemon (pollita@php.net):
> > Can this not be done easily with array_walk?
> >
> Yes, though the primary purpose here is to have a method to create a
> form-encoded query string internally, exporting it to userspace is just a
> "why the heck not" side-effect.
Ahh.. ok.
>
> > I think this might also encourge people to use extremly long query
> > strings, which will break when it gets to a certain length. I
> > believe, off hand, 255 bytes is what is suggested max length for a
> > query string.
> >
> For HTTP/1.0 GET query_strings yes (2048 bytes for HTTP/1.1 GET), but for
> POST data (which uses the same form encoding) the length of the query string
> is not limited.
I did have a feeling 255 was a bit small, thanks for clarifying
that for me.
>
> Note: I don't have a great deal invested in this, if there's no desire to
> use this my heart won't be broken.
My second thought was to perhaps apply this to urlencode so
urlencode would be defined as:
string urlencode(mixed expression)
Although this sort undefines what exacly urlencode does and might
lead to even more confusion.
Curt
--
"I used to think I was indecisive, but now I'm not so sure."