Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92225
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAJaRsPvzG8iVm3O2Nz5k=djt0e2HqB-jmQBDb8BysbxfvfhUFg@mail.gmail.com>
References: <570C9101.5060500@php.net>
	<CAJaRsPvzG8iVm3O2Nz5k=djt0e2HqB-jmQBDb8BysbxfvfhUFg@mail.gmail.com>
Date: Tue, 12 Apr 2016 20:21:52 +0700
Message-ID: <CAEZPtU5UKB06TofSdiwNyKUm75y9o7YKbsA8i=9=i4=EZxGfgQ@mail.gmail.com>
To: "Colin O'Dell" <colinodell@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Sebastian Bergmann <sebastian@php.net>
Content-Type: multipart/alternative; boundary=001a11c1d3426e97120530498bf7
Subject: Re: [PHP-DEV] UUID
From: pierre.php@gmail.com (Pierre Joye)

--001a11c1d3426e97120530498bf7
Content-Type: text/plain; charset=UTF-8

On Apr 12, 2016 7:56 PM, "Colin O'Dell" <colinodell@gmail.com> wrote:
>
> On Tue, Apr 12, 2016 at 2:09 AM Sebastian Bergmann <sebastian@php.net>
> wrote:
>
> > In PHP 7.0 we introduced random_bytes() which wraps Linux's getrandom(2)
> > as well as Windows's CryptGenRandom() and uses /dev/urandom as a
fallback.
> >
> > I think it would be great if we added a function that wraps
> > /proc/sys/kernel/random/uuid [2] and, if that exists, its equivalent on
> > Windows to make the generation of UUIDs easy.
> >
> > Thoughts?
> >
>
> I'd love to see UUID generation in core using a similar platform-based
> approach, as long as the implementation matches RFC 4122.  Part of this
> will be determining which versions/variants should be supported:
>
https://en.wikipedia.org/wiki/Universally_unique_identifier#RFC_4122_Variant
>
> Version 4 (random) UUIDs is an obvious choice, but should any others be
> supported initially?
>
> Perhaps the implementation could be a simple function named random_uuid()
> which either takes no parameters or a single parameter "$version" which
> defaults to 4?

I would prefer not to refer to random to avoid any confusion with the
recent added random function. As uuid is not crypto safe and is not aimed
to. Users will then hopefully not think about using instead of the random
api.

Also uuid alone may be a problem (bc?) It sounds like a logical choice.
Alternatively uuid_create ().

Cheers
Pierre

--001a11c1d3426e97120530498bf7--