Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4254
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sat, 30 Aug 2003 03:10:58 +0000
To: internals@lists.php.net
Message-ID: <20030830031058.GB92919@bagend.shire>
Mail-Followup-To: internals@lists.php.net
References: <20030828211521.99071.qmail@pb1.pair.com> <20030829060724.GC92919@bagend.shire> <20030829190112.58021.qmail@pb1.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030829190112.58021.qmail@pb1.pair.com>
User-Agent: Mutt/1.4.1i
Subject: Re: [PHP-DEV] Proposed Function: urlencode_array
From: php-dev@zirzow.dyndns.org (Curt Zirzow)

* 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."