Works for me - I'm getting tired of deleting all those directories between test/debug sessions! :-)
As for the polarity, you can always make a case for inheriting a default from the router - in other words, add a setting to the router persistence declaration for default opt-in or opt-out, and then let the resource add explicit opt-in or opt-out overrides. So for my case, router persistence would be default opt-out, and the ServiceGroup would opt-in. It's a thought... Cheers, Joel -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 16, 2006 5:00 PM To: [email protected] Subject: Re: Possible Persistence enhancement how about an attribute on <resource-type/> called "use-router-persistence", of type boolean? the default value would be tricky. I could easily make a case for both values. however, when I think about some of the "real" products we've tried to model with the code, I lean towards a default value of "false"; that is, I think a lot of "real" WSDM endpoints will fall under the use case described in your email. Dan "Hawkins, Joel" <[EMAIL PROTECTED]> wrote on 08/16/2006 12:53:53 PM: > Musers, > > The current implementation of persistence doesn't retain some of the > semantics of the original "startup-count". One use case that isn't well > served is the case where a ServiceGroup is desired at startup, but the > contents of the service group are always added dynamically. At present, > persistence is a function of the router definition, and there's no > opt-out (or opt-in, we can debate which is more appropriate) ability at > the resource definition level. > > What does everyone think of making persistence override-able at the > resource definition level? > > Cheers, > Joel > > The contents of this e-mail are intended for the named addressee only. It > contains information that may be confidential. Unless you are the named > addressee or an authorized designee, you may not copy or use it, or disclose > it to anyone else. If you received it in error please notify us immediately > and then destroy it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
