On Oct 3, Tom Cook quoth:
> [EMAIL PROTECTED] writes:
> > On Sep 29, Peter Jasko quoth:
> [snip]
> > While this is far from a formal analysis of the likelihood of failure, it
> > is very small for any reasonable usage whereas your algorithm has a
> > failure probability of 1 in the event of the high bit generator being
> > unavailable.
>
> Erm, in the context of EJBs, if your high bit generator is also your
> database then unavailability of the high bit generator is also
> unavailability of the EJBs which use it, yes?
If you only have one database installation which contains all your data
and everything you are running is in one box in one location in one hard
drive without the need to operate in a degraded state or have graceful
failover then, yes, then you are correct, there is no need for a
distributed unique id generation system.
In fact, it would be silly in such circumstances to try and reduce the
amount of interdependence between your database vendor's proprietary
implementation of key generation and your portable, write once, run
anyhere, database-issues-are-the-containers-problem Enterprise Java Beans.
I don't know what I was thinking. I stand corrected.
C=)
--------------------------------------------------------------------------
The fact that no one understands you doesn't mean you're an artist.
--------------------------------------------------------------------------
Caskey <caskey*technocage.com> /// TechnoCage Inc.
--------------------------------------------------------------------------
Oh no! Space monkeys are attacking! -- eddie izzard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
