> From: Berin Loritsch [mailto:[EMAIL PROTECTED] > > @avalon.scope -- Used to represent the scope of the component, > and consequently the lifestyle. Values are > "container", "thread", and "request" I was wondering if it isn't better to explicitly specify what the scope will result in, rather than trying to abstract away from it.
Thus, we'd have "singleton" instead of "threadsafe"/"container", "pooled" instead of "request". It seems like everyone equates ThreadSafe -> Singleton anyway, and honestly this abstraction isn't really giving us very much. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
