Ok, excellent, many thanks. I'm going see if I can spike something simple and go from there.
On Wed, Oct 21, 2009 at 1:56 PM, Ayende Rahien <[email protected]> wrote: > RQ means that you don't need anything installed on the client, but you get > persistent queues support. > If you don't care about persistent queues, you can implement an in memory > transport. > > RSB provides the bus, it relies on an underlying queue impl. > Currently we support both MSMQ and RQ > > Zero admin means that you don't need to install a service, setup queues, > etc. It is just running in your app. > > > On Wed, Oct 21, 2009 at 7:47 PM, Everett Muniz <[email protected]>wrote: > >> thanks for the response Oren! >> I feel like I'm asking inane questions so I apologize if that's the case. >> architecturally, i'm really attracted to what's appears to be possible in >> the service bus scenario but I'm really green on the concept and even more >> so on the tools and how to use them. I'm feeling my way here - these are >> questions out of genuine ignorance. >> >> i gather RSB + RQ means combing the Service Bus with Queue project. why >> would I need to combine the 2 projects? >> >> also, when you say "zero install footprint" could you unpack that a bit. >> are you saying that the core RSB assemblies with relevant referenced >> assemblies would be all that the install would need to include. i wouldn't >> need to do anything relative to msmq? >> >> is there a reference app anywhere that shows what using RSB in this >> context might look like? >> >> >> On Wed, Oct 21, 2009 at 1:28 PM, Ayende Rahien <[email protected]> wrote: >> >>> You can certainly do that. >>> You can use RSB + RQ to have a zero install footprint. >>> Although you probably want to patch RQ so it wouldn't go over the network >>> to pass messages around. >>> >>> >>> On Wed, Oct 21, 2009 at 7:15 PM, everettmuniz <[email protected]>wrote: >>> >>>> >>>> It looks like the service bus concept is more typically applied to >>>> distributed scenarios. I'm extremely new to the service bus world but >>>> I was recently asking around on the NHibernate list about the best >>>> approach to developing a multi screen desktop app where you might >>>> have several screens open and want each to have it's own session >>>> (http://groups.google.com/group/nhusers/browse_thread/thread/ >>>> 706451ca38599b4d?hl=en<http://groups.google.com/group/nhusers/browse_thread/thread/%0A706451ca38599b4d?hl=en>) >>>> There's some work that has been done in the >>>> unhaddins project to address this scenario but someone else suggested >>>> considering tackling the problem with a service bus. >>>> >>>> I've been looking at RSB and it's provoked a couple of questions: >>>> (1) our project is a totally self contained desktop app, is a service >>>> bus considered a reasonable solution in that context >>>> (2) our product will be a commercial application that users will >>>> download and expect to install easily -- is there anything about that >>>> scenario that would rule out RSB? >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
