Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4253 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58046 invoked by uid 1010); 29 Aug 2003 19:01:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 58022 invoked by uid 1007); 29 Aug 2003 19:01:12 -0000 Message-ID: <20030829190112.58021.qmail@pb1.pair.com> To: internals@lists.php.net References: <20030828211521.99071.qmail@pb1.pair.com> <20030829060724.GC92919@bagend.shire> Date: Fri, 29 Aug 2003 12:02:28 -0700 Lines: 21 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Posted-By: 169.229.135.140 Subject: Re: [PHP-DEV] Proposed Function: urlencode_array From: pollita@php.net ("Sara Golemon") > 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. > 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. 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. -Sara