Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96512 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46727 invoked from network); 20 Oct 2016 10:12:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Oct 2016 10:12:17 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.50 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.213.50 mail-vk0-f50.google.com Received: from [209.85.213.50] ([209.85.213.50:32836] helo=mail-vk0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 00/14-24564-D7898085 for ; Thu, 20 Oct 2016 06:12:15 -0400 Received: by mail-vk0-f50.google.com with SMTP id 83so64460260vkd.0 for ; Thu, 20 Oct 2016 03:12:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4hfMvrqxJ7HI5vXOcPudo8hITYlDalUQ67jG2cwuNSE=; b=a5+ub9bPIstbcXJpFM3TlNBjUWF4Zs2KjuZrlIccw4zfUWMuu86QPm1w4UXvNvloIv WjlyDevgK5tcs9Txp9oHh5lsQzVxcuDJ9x1Vj4zgC3tgpuL1/pIPT1lZYQ87a7G+ukeX gtVrQ6a/3r5Ulj4ZEeZW2kd9wvK5VbjlEXz6VQXeqNMWLCSkzvjnO7WpHkNbXsVH2OOi aBa+Uygxl4m3xP9I3EatvqBUcCVNoT7LBfpy541wnX5pkZs36PWHovxkbBprqzK83MaZ nnyBNWnqLWORFWF1NlNWUiZMsrrE7MXix8MrhZjDr19Q1yb0Fv+ONSYAVk1Dz/mdu5I/ EXgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4hfMvrqxJ7HI5vXOcPudo8hITYlDalUQ67jG2cwuNSE=; b=eUBHFi4K11lamMj6VS+eH0nxtjZzmztZihggOy3EMBSMkrvaV15DeRPrvoVhtOr8ZT KvXw9Vdfc2Jwn4EHNyGOzPNg0HU53NgUprtBefQj2gXADedT+9iYzjG4uwXAlESIGPtC 5XnLI5iPaQi3J3eCCaYU385FOc5RW5CfOrtc3c9S2Ew1JiN9OHlsc3Lc71o8CElmebh/ YuvNYh4c+WdkD8H/sGq1gcjYVKTRWgXuPOD7oCcwuVhvEh6TJ+nC8hTj58JFSdFavEWw 0UcXSNlVuv/siOw736e1YknBe8Nfi/DKLkiSZE5gHH+Dtg/jjOjQa2O4ukutdh9qVPiw mQMQ== X-Gm-Message-State: AA6/9RmMX0IFUs+ACoioqpSO9zfp0QIDvdb/0ZmhbJi0J9L3uOjN5RkKuxRUSjqBQeNgfmhKgjuv859va6yi7A== X-Received: by 10.31.52.66 with SMTP id b63mr10042688vka.9.1476958331193; Thu, 20 Oct 2016 03:12:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.36.109 with HTTP; Thu, 20 Oct 2016 03:12:10 -0700 (PDT) In-Reply-To: References: <070001d2295e$76b7d730$64278590$@belski.net> <075a01d22993$9efc6c80$dcf54580$@belski.net> <088801d229fa$d7320cb0$85962610$@belski.net> Date: Thu, 20 Oct 2016 17:12:10 +0700 Message-ID: To: Yasuo Ohgaki Cc: Kalle Sommer Nielsen , Anatol Belski , Joe Watkins , Niklas Keller , Leigh , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Improve uniqid() uniqueness From: pierre.php@gmail.com (Pierre Joye) On Thu, Oct 20, 2016 at 4:44 PM, Yasuo Ohgaki wrote: > Application requires unique ID under across multi process/thread > tasks, it will have more chance to have collided unique ID. uniqid fill(s|ed) some needs or maybe still fits for some. However for modern application with many concurrent requests or nodes, it does not fit anymore, since long. Do we need to fix a broken hammer to fix the screw? I do not think so. I suggested already to simply improve it if we can do it without breaking BC and recommend to use something designed for such tasks, UUID. ramsey/uuid is one of them, other are available. Cheers, -- Pierre @pierrejoye | http://www.libgd.org