> -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: den 8 april 2004 19:52 > To: '[EMAIL PROTECTED]' > Subject: RE: [Kernel22] How to develop a component? > > > I think you have captured this pretty well. Some thoughts: > > ALT1 - IMO the disadvantages are worse than they appear. > Yes, distributed apps and DB connections exhibit this > behavior, but when you are talking about ALL the cocoon > components having this behavior the code will turn into > nothing but error handling logic. This is just plain > non-workable in my view. > > ALT2 - Hmmm. You want to hot swap a singleton? Can you EVER > really do that?
I have situations where you can have zero or one instance, but not two or more. For example, a DB has an upper limit to the number of connections it can handle. If a component is a client of the DB (it is a connection pool), I want to know that I either have no connection pool, or exactly one connection pool. If you suddenly run two side-by-side, then the new pool will never acquire a connection, while the old one will hold on to the ones it has acquired until it is released (and who knows when that may be). /LS
