Multi-process access in Heroku environment causes PubNub initialization to occasionally fail about ruby HOT 7 CLOSED

Thanks for notice @rafalyesware, i'm checking it and i will apply fix asap.

from ruby.

Thanks @blazeroot. FWIW, all the Ruby UUID gems seem to have some failing or another... I don't know if you really need a UUID or just a large unique value, but if you can do without a proper UUID the Mongo ObjectID seems like a great choice (c.f. http://docs.mongodb.org/manual/reference/object-id/) for multi-host / multi-process environments.

from ruby.

@blazeroot FWIW, we don't need EXACTLY per the UUID-spec, just a UUID-like pattern that has an equivalent duplicates collision domain within its own alogrithm, and UUID's.

from ruby.

Fixed and tested. @rafalyesware please use master branch of pubnub and let me know if that helps.
ps. SecureRandom doesn't exist in 1.8 and we want pubnub to be compatible with ruby1.8.

from ruby.

You guys are all right! 👍 Will try to pull this in to our code ASAP, thanks!

from ruby.

@blazeroot Pulled the latest gem off master and it is working as promised. Thanks for the quick turnaround!

from ruby.

@rafalyesware No problem! I'm happy to hear that!

from ruby.