Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98376
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.193 as permitted sender)
Date: Thu, 02 Mar 2017 14:34:07 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CACMzB5fHeuTumzRATTyj1K_CN77P1_on1qvOgY_C1=su6H54Mg@mail.gmail.com>
References: <CACMzB5fHeuTumzRATTyj1K_CN77P1_on1qvOgY_C1=su6H54Mg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Rene Veerman <rene.veerman.netherlands@gmail.com>
Message-ID: <E3586D40-3D2C-40F8-9397-407B05039BD5@gmail.com>
Subject: Re: [PHP-DEV] please excuse my forum crosspost, please do read this when you have some time.
From: rowan.collins@gmail.com (Rowan Collins)

On 1 March 2017 20:30:42 GMT+00:00, Rene Veerman <rene=2Eveerman=2Enetherla=
nds@gmail=2Ecom> wrote:
>exec-sum : introducing a new URL notation scheme

I'm not at all sure what you're trying to achieve here, and if you wanted =
this to be widely adopted, I think you're about 30 years too late=2E

What is the "elevator pitch" for this syntax? Why would I choose your synt=
ax over the long-established "?foo=3Dbar&baz=3Dquux" syntax?


>example 1 :
>
>http://localhost/tarot(deck'Original-Rider-Waite
>',reading'3-Cards')/music(youtubePlaylist'ABCDEFG')

In PHP, you will get your desired result using http://localhost/?tarot [de=
ck]=3DOriginal-Rider-Waite&tarot[reading]=3D3-Cards&music[youtubePlaylist]=
=3DABCDEFG

It's slightly more verbose if you have lots of items in one array, but has=
 the crucial advantage that you can use standard HTML forms to generate it=
=2E


>http://localhost/jsonViewer(url'base64aHR0cDovL3NlZHVjdGl2ZWFwcHMuY29tL2p=
zb24ucGhwP2ZpbGU9L2hvbWUvcmVuZS9kYXRhLmpzb24mdmVyc2lvbj1jb25kZW5zZWQ=3D

Using base64 in URLs is already quite common; there's no standard way of a=
nnotating it to be automatically decoded, but creating a convention in your=
 own application is not difficult - normally as simple as "this field is al=
ways base64, everything else never is"=2E


Maybe I'm missing something, but your linked post doesn't seem to give any=
thing more than these same examples=2E And since this is the mailing list f=
or developing the internals of the PHP language, what is it you think shoul=
d be added to the language for this?

Regards,

--=20
Rowan Collins
[IMSoP]