A normally registered service in Windsor seems to life as a singleton. In a web application, it looks like a good pattern to pass a service nothing (or very little else) than other services that also can be resolved by the container. Anything with weight you pass in the service's methods. So the services, even as singletons are very light-weighted.
Still the singleton nature worries me a bit. How do you handle this? What lifecycles do you use for which kinds of services? Does PerWebRequest really create an instance on every web request or only if there is demand? How does this affect performance? -- Jan ___________________ [EMAIL PROTECTED] www.limpens.com +55 (11) 3082-1087 +55 (11) 3097-8339 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
