Makes sense to me. I think one of the shortcomings of fluent interfaces are that it is often hard to extend them in an elegant way.
Maybe at least add a ///<summary> to the Rhino-only members of HostConfiguration to make it clear that they only apply when configuring a Rhino queue? On Aug 15, 1:53 pm, Corey Kaylor <[email protected]> wrote: > https://github.com/hibernating-rhinos/rhino-esb/pull/29 > > On Mon, Aug 15, 2011 at 11:42 AM, Ken Baltrinic <[email protected]>wrote: > > > > > > > > > Commit f13eedf3023901e78b11 moved the storage path setting from > > RhinoQueuesHostConfiguration to HostConfiguration. I am must curious > > as to the reason for this. I created RhinoQueuesHostConfiguration > > when I added the storage path setting because the setting only applies > > if using RhinoQueues. It didn't seem to make sense to clutter up the > > HostConfiguration interface with such settings. > > > This is not a critical post. I have no objections to the change. > > Just trying to understand if my approach lead to problems or what the > > issue was. > > > --Ken > > > -- > > You received this message because you are subscribed to the Google Groups > > "Rhino Tools Dev" 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/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
