Giter Site home page Giter Site logo

Possible extension of v1 UUIDs about uuid HOT 8 CLOSED

uuidjs avatar uuidjs commented on July 16, 2024
Possible extension of v1 UUIDs

from uuid.

Comments (8)

broofa avatar broofa commented on July 16, 2024

Christoph, let me think about this. My initial reaction is that what you're proposing here seems like a special case of the "compose a UUID" problem, which may be better addressed by having a utility method that allows you to specify some/all of the fields defined in sect 4.1, and composes the UUID for you. (And writing that is probably non-trivial and likely to add significant code bloat.)

Let's leave this out of the v1 diff for now and wait until we've got some concrete examples of how people might need/use this before moving forward here.

from uuid.

broofa avatar broofa commented on July 16, 2024

[reopening in case others have thoughts on this]

I could see doing something like the following. Maybe. :) ...

function uuid([options[, buffer[, offset]]])

  • options - options object, may contain...
{
  random: (Array)      // (v1/v4) random #'s to use instead of rnds
  format: (String),    // (v1/v4) equivalient to current 'fmt' argument,
  timestamp: (Number), // (v1) timestamp to use
  clockseq: (Number),  // (v1) clockseq to use
}
  • buffer - Array/buffer to write into
  • offset - offset into buffer to begin writing

Thoughts?

from uuid.

ctavan avatar ctavan commented on July 16, 2024

Looks good to me. Especially since we don't have to break anything to make it work.

from uuid.

pnegri avatar pnegri commented on July 16, 2024

Following this close. Keep good work.

from uuid.

ctavan avatar ctavan commented on July 16, 2024

If we do this, we should allow specifying the node as well. Maybe somebody has access to the mac-address and really wants RFC compliant v1 uuids...

{
  random: (Array)      // (v1/v4) random #'s to use instead of rnds
  format: (String),    // (v1/v4) equivalient to current 'fmt' argument,
  timestamp: (Number), // (v1) timestamp to use (in UNIX epoch)
  clockseq: (Number),  // (v1) clockseq to use
  node: (Number) // (v1) node. it's a 48bit integer, so maybe we must use a byte-array?
}

Another thing: we measure times in UUID epoch throughout the lib now, but I think when specifying a timestamp as an option we must use UNIX-time to avoid confusion.

from uuid.

ctavan avatar ctavan commented on July 16, 2024

I have added a pull request for this one, I think we can continue discussion there: #16

from uuid.

pnegri avatar pnegri commented on July 16, 2024

about the node value i was thinking about using a byte replace in only node part at the client or util. trying to dont add boilerplate. but its great like that.

from uuid.

broofa avatar broofa commented on July 16, 2024

we must use UNIX-time to avoid confusion

agree.

from uuid.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.