Comments on: UUID generator for PHP

By: Lysender

Lysender — Wed, 10 Mar 2010 05:16:21 +0000

I have modified them so that it will convert binary back to string or byte etc

static private function conv_bin2byte($src) {
// array_merge – reindex since unpack starts at index 1
return array_merge(unpack(’C16′, $src));
}

static private function conv_bin2field($src) {
$byte = self::conv_bin2byte($src);
return self::conv_byte2field($byte);
}

static private function conv_bin2string($src) {
$byte = self::conv_bin2byte($src);
return self::conv_byte2string($byte);
}

By: Lysender

Lysender — Wed, 10 Mar 2010 04:44:24 +0000

How do I convert a binary back to string or byte or field?

Uuid::convert($id, Uuid::FMT_BINARY, Uuid::FMT_STRING)

is not yet supported. It is just now that I notice the problem.

By: Universally Unique Identifier (UUID) in PHP und MySQL » Webmaid.de

Universally Unique Identifier (UUID) in PHP und MySQL » Webmaid.de — Thu, 25 Feb 2010 08:45:08 +0000

[...] und als Klasse bereit gestellt. Bei der Suche im Netz habe ich zwei Varianten entdeckt: DrUUID und UUID Generator. Außerdem kann man auch das PECL Package uuid nutzen, welches jedoch die libuuid (des Projekts [...]

By: Gavitron

Gavitron — Thu, 17 Dec 2009 20:58:25 +0000

Actually, after several hours of testing, I have identified a significant bug in this implementation. If you generate a version 3 or 5 UUID, using a namespace UUID with the first byte > 8, your code overflows, and generates invalid UUIDs. further, this invalid UUID is the same for all namespace UUIDs >80000000-0000-0000-0000-00000000000

By: David

David — Tue, 25 Aug 2009 20:33:17 +0000

Thanks for the great class!

One note is that many implementations claim that the example for version 3 as shown in RFC4122 is incorrect (OSSP uuid, python) where the value generated should actually be 3d813cbb-47fb-32ba-91df-831e1593ac29. If one needs compatibility with these (and other) libraries for version 3/5 one can remove lines 163-165 and 180-182 (byte swapping lines) and get matching results.

By: fli

fli — Tue, 07 Jul 2009 14:01:49 +0000

The bugs mentioned in the posts above should have been fixed now.

By: jonovic

jonovic — Wed, 27 May 2009 13:26:35 +0000

I’ve tried on Php 5.2.6 on Windows and fall into trouble with random generation. Time_low part is generated using mt_rand with interval set to 0,0xffffffff. The mt_rand function however uses signed integer for parameter and that’s why the resulting value is always negative. When passing to sprintf the result of time_low part is always 0.

By: conzio » Die UUID «

conzio » Die UUID « — Sun, 03 May 2009 07:32:29 +0000

[...] besonders anspruchsvolle Situationen und Sicherheitsfanatiker hat ‘fli’ einen UUID-Generator geschrieben, der keine Wünsche offen [...]

By: J. King

J. King — Sat, 11 Apr 2009 19:23:37 +0000

I was very excited to see your implementation of RFC4122, because I was looking to use UUIDs for Atom and didn’t want something merely “UUID-like” as all these other PHP implementations are. However, I hate to break it to you, but your implementation of Version 1 UUIDs seems to be broken in a number of ways. Besides the clock sequence (which is understandable) your implementation seems to use a null MAC node (whereas it should generate a random one), but worst of all the encoding of the time is completely wrong! If you plug the output of your generator into the time extractor at http://www.famkruithof.net/uuid/uuidgen?typeReq=-1 (which I know to be correct: I checked with known timestamp values) you’re left with a time several centuries from now. If you use a date in the past the disparity is even greater (several -millennia- from now…). I just thought you should know.

If you’re curious I also wrote my own implementation from scratch yesterday since I had no one to depend on but myself (and I didn’t like your API anyway—sorry). I’d very much like to know what you think of it.

http://jkingweb.ca/code/php/lib.uuid/

By: Konrad

Konrad — Sun, 22 Feb 2009 20:38:11 +0000

Thank you.