Obviously, if I declared it as NonSwappable hot swapping would not be allowed - at least for the class (that doesn't mean the rest of the block couldn't be swapped, but that complicates matters).
I guess I can envision 3 "types": NonSwappable - can't ever be hotswapped. Swappable - should be swapped using ALT3 Nothing declared - should be swapped using ALT2. Ralph -----Original Message----- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 12:45 PM To: [EMAIL PROTECTED] Subject: Re: [Kernel22] How to develop a component? Ralph Goers wrote: > is managing stuff that is supposed to be permanently available. In this > case your singleton is no longer a singleton. Frankly, I'd suggest that > classes meant to be singletons should implement a Singleton (or NonSwappable > or whatever) interface to prevent them from ever being reloaded. By the way > - I think this is a problem for ALL the alternatives, not just this one. > > ALT3 - From a client perspective, this looks just like ALT2. The client does > a lookup that obtains a read lock while release does the unlock. > > Since the Singleton thing makes no sense to me anyway, I'd say use ALT2. Ralph, what about when you want to hotswap your singleton to a new version? -- Stefano.
