Hi all.
With NHibernate now supporting the client profile, I'd like to see
client profile support for Castle.ActiveRecord. Unfortunately, as far
as I can see, there's no easy way to do it. SessionScopeWebModule is
an IHttpModule and people configure it by providing the qualified
class name in the httpModule section of the config file. I don't see
how to fix that without moving SessionScopeWebModule to a separate
assembly or using compilation directives. For comparison, NLog has
gone through a similar process and split the web components into a
NLog.Extended to match the split between the client and extended
frameworks. I'd like to suggest a couple possibilities.
1. Split off at least SessionScopeWebModule (and potentially other
web things) into a Castle.ActiveRecord.Extended (or
Castle.ActiveRecord.Web) assembly. This would be a breaking change
requiring certain web users to add a reference to the new project.
2. Use #ifdefs and distribute two different versions of the
Castle.ActiveRecord assembly. One for web, one for not.
My personal preference is #1, since it is a one time change, even if
it's a breaking change. The second one causes all sorts of
distribution / build headaches as mentioned in my other message
pertaining to Castle.Core.
What are people's thoughts on this?
Patrick Earl
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" 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-devel?hl=en.
