The traditional way to handle it is to have a central database the assigns numbers and increments a counter. The problem with is the central database may be inaccessible. Further the central database becomes a crucial bottleneck.
I suggest a partially decentralised variant in my Unique Number Server Student Project.
Another way to do it is to use large pseudorandom numbers and count on the improbability of two numbers being picked the same. This technique is fully decentralised approach. No communication between number assigners is needed. This is how java.util.UUID works.
![]() |
and suggestions to improve this page to Roedy Green : | ||
| Canadian Mind Products | |||
| mindprod.com IP:[65.110.21.43] | |||
| Your face IP:[38.103.63.62] | The information on this page is for non-military use only. | ||
| You are visitor number 4,687. | Military use includes use by defence contractors. | ||
| You can get a fresh copy of this page from: | or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror) | ||
| http://mindprod.com/jgloss/unique.html | J:\mindprod\jgloss\unique.html | ||