I am planning to use an implementation of ISubscriptionStorage that uses an SQL Server database table, while still using MSMQ as the transport, and my question is along the lines of what the best practice for replacing subscription storage is.
What I have noticed is that the MsmqTransportConfigurationAware class looks for an endpoint with a scheme of "msmq", and if it finds one, it configures MSMQ transport and MSMQ subscription storage. I cannot really see a hook to replace the ISubscriptionStorage implementation in this class. So do I create my own class that implements IBusConfigurationAware and configures a combination of MSMQ transport with my database-backed subscription storage, or is there a better way than that? Has anyone done this kind of thing before? I'm still finding my way a bit, and do not want to head off in a direction that has been tried before and found to be the wrong direction. (Out of interest, if anyone is wondering why I want to replace the MSMQ subscription storage, it is because I have smart client applications that registering and unregistering instance consumers, and if I use the MSMQ subscription storage for this, the message queue gets very big very quickly). -- 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.
