While speed in this context is an issue i can work around this by creating a large enough set of row ids before catering to any request right?
Any modern computer can generate millions of objects in a millisecond. So System.currentTimeMillis() is too slow.
Can i work around this using thread synchronisation and separate the row id generation routines from being thread aware? I mean when a new thread is spawned, each thread does not create a new row id, but rather fetches a row id from a collection of possible values. This fetching can be thread safe and the creation process of row ids can be separated.
If your program is multi-threaded and you have a multi-core CPU, then different cores might be creating objects at the same time
This is problematic. Will think on this. Any comments on the above?
If the system clock is adjusted