• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Globally unique IDs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Globally unique IDs


  • Subject: Re: Globally unique IDs
  • From: Alexander Spohr <email@hidden>
  • Date: Sun, 8 Feb 2004 13:54:05 +0100

Am 08.02.2004 um 12:40 schrieb Alexander Spohr:

public EOTemporaryGlobalID()
Creates and returns an EOTemporaryGlobalID as a unique instance. The returned object contains a byte string that's guaranteed to be unique network wide. As a result, EOTemporaryGlobalIDs can be safely passed between processes and machines while still preserving global uniqueness. The returned byte string has the format:


< Sequence [2], ProcessID [2] , Time [4], IP Addr [4] >

if i check my EOTemporaryGlobalIDs i get strings like this:

 0 0 10 0 1 50 0 0 8 -82 3 0 0 0 0 -6 -107 26 47 43 -19 127 38 -82
 0 0 10 0 1 50 0 0 8 -82 2 0 0 0 0 -6 -107 26 47 43 -19 127 38 -82
 0 0 10 0 1 50 0 0 8 -82 1 0 0 0 0 -6 -107 26 47 43 -19 127 38 -82

     [my ipv4]         [seq]

EOTemporaryGlobalID.UniqueBinaryKeyLength returns 24.
so the EOTemporaryGlobalID docs are wrong about
a) the size
b) the content.

has anyone an idea what the real parts of those 24 bytes are?

	atze
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Globally unique IDs (From: "Colin O'Brien" <email@hidden>)
 >Re: Globally unique IDs (From: Ben Trumbull <email@hidden>)
 >Re: Globally unique IDs (From: Pierre Frisch <email@hidden>)
 >Re: Globally unique IDs (From: Alexander Spohr <email@hidden>)

  • Prev by Date: Re: Globally unique IDs
  • Next by Date: Best methodology for reusable components
  • Previous by thread: Re: Globally unique IDs
  • Next by thread: Re: Globally unique IDs
  • Index(es):
    • Date
    • Thread