{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/3bc5e1eb910b307b5b723f9fa25db108?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3bc5e1eb910b307b5b723f9fa25db108","url":"https://api.github.com/users/ctavan","login":"ctavan","id":508118},"labels":[],"assignee":null,"updated_at":"2011-11-17T13:45:43Z","closed_at":null,"comments":2,"url":"https://api.github.com/repos/pnegri/uuid-js/issues/10","body":"During the past few days I've been working on integrating v1 UUID's into the lightweight node-uuid module, see https://github.com/broofa/node-uuid/pull/11\r\n\r\nThe node-uuid implementation is a lot faster than uuid-js while still remaining RFC compliant. However it doesn't add so many convenience methods as this library does.\r\n\r\nMaybe it's worth the idea to port the genarting-part from node-uuid to uuid-js? Or maybe even restructure uuid-js as a highlevel wrapper around node-uuid? I'm curious about your thoughts.","html_url":"https://github.com/pnegri/uuid-js/issues/10","title":"Use faster UUID generation","number":10,"id":2268551,"created_at":"2011-11-17T13:12:54Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/3bc5e1eb910b307b5b723f9fa25db108?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3bc5e1eb910b307b5b723f9fa25db108","url":"https://api.github.com/users/ctavan","login":"ctavan","id":508118},"updated_at":"2011-11-17T13:45:43Z","url":"https://api.github.com/repos/pnegri/uuid-js/issues/comments/2776025","body":"True, UUID-generation will probably not be a bottleneck, but if we can have it fast, why not use it?\r\n\r\nI'll put up a benchmark. I guess including node-uuid for UUID-generation might really be an option, so we don't re-invent the wheel here...","id":2776025,"created_at":"2011-11-17T13:45:43Z"}}