Maybe that it requires SQLServer to be installed? ;) On Sun, Nov 1, 2009 at 08:20, Martin Nilsson <[email protected]> wrote:
> Cool! > What makes it fail regarding xcopy requirement? > > > On Sat, Oct 31, 2009 at 2:48 PM, Corey Kaylor <[email protected]> wrote: > >> I have a branch in my fork of the project that has initial support for SQL >> Service Broker. It has a few known bugs and improvements I haven't had time >> to work through yet, but yes it does make a few scenarios nice. I >> specifically started working on it because of a few items below I felt were >> nice to have. I'm not sure if Ayende will want this in the project after I >> work through the issues though, it goes against the xcopy deployment >> requirement. >> >> 1. Can setup a notification queue to notify when to start processing >> messages, rather than a Thread.Sleep polling mechanism. >> 2. Two nodes can share the same queue, but also be addressed inidividually >> (in my implementation of subqueues). >> 3. Depending on the SQL Server setup and queue deployment setup you can >> have full failover where there is no loss of time in message processing. >> 4. Does not require DTC, but still supports it if necessary. >> 5. It's fast. When I'm done I will setup a comparisson on its performance >> over the other transport implementations. >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
