Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72415
Return-Path: <anatol.php@belski.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 14719 invoked from network); 8 Feb 2014 22:19:10 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 8 Feb 2014 22:19:10 -0000
Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
X-PHP-List-Original-Sender: anatol.php@belski.net
X-Host-Fingerprint: 85.214.73.107 klapt.com  
Received: from [85.214.73.107] ([85.214.73.107:39879] helo=klapt.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 30/20-12906-C5DA6F25 for <internals@lists.php.net>; Sat, 08 Feb 2014 17:19:08 -0500
Received: by klapt.com (Postfix, from userid 33)
	id 454AC23D611B; Sat,  8 Feb 2014 23:19:05 +0100 (CET)
Received: from 178.2.17.83
        (SquirrelMail authenticated user anatol@belski.net)
        by webmail.klapt.com with HTTP;
        Sat, 8 Feb 2014 23:19:05 +0100
Message-ID: <d928ffdd7079d8998a982bcc73ef78e0.squirrel@webmail.klapt.com>
In-Reply-To:
 <CAGa2bXbw02kGbiMvTyJSU4EtJjNGt6KP4mH5o8s+=AiTMYVWHQ@mail.gmail.com>
References:
    <CAGa2bXbw02kGbiMvTyJSU4EtJjNGt6KP4mH5o8s+=AiTMYVWHQ@mail.gmail.com>
Date: Sat, 8 Feb 2014 23:19:05 +0100
To: "Yasuo Ohgaki" <yohgaki@ohgaki.net>
Cc: "Pierre Joye" <pierre.php@gmail.com>,
 internals@lists.php.net
User-Agent: SquirrelMail/1.5.2 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] uniqid() is not unique under windows
From: anatol.php@belski.net ("Anatol Belski")

Hi Yasuo,

On Sat, February 8, 2014 22:14, Yasuo Ohgaki wrote:
> Hi Pierre,
>
>
> Why is uniqid() is not guarantee uniqueness under windows?
>
>
> https://bugs.php.net/bug.php?id=65626
>
its base are microseconds, so nothing prevents to usleep() in user space.
It's also documented to be nonsecure, so isn't it just the expected
behavior?

> It seems PHP_WIN32 and __CYGWIN__ check is obsolete.
> Could it be removed?
>
Never compiled with cygwin. However what stands in the code might be true
needed, as cygwin is proxying native APIs, so it is expected to be much
slowlier. Maybe there are other reasons for that, though.

Regards

Anatol