Thanks for the info and quick replies guys. You were exactly right, Corey. The web site is configured using payment.client and the service is using payment.service.
I have a follow-up question: There are multiple instances of the web site, one for each of our customers... they essentially rebrand our core offering. Can they all use the same queue defined in payment.client? That also seems to be working, and I'm baffled as to why, although that is a bit less confusing to me since there could be some IDs passed around. But it would seem that it might be more efficient to have a unique client queue for each site? I just kinda envision RSB publishing events out to all the subscribers (basically every site) needlessly. BTW, sagas are awesome. I was able to implement some post-payment functionality for all sites merely by adding some behavior to a single saga. Thanks again, == Ross-a-roni == On Tue, Nov 30, 2010 at 4:20 PM, Corey Kaylor <[email protected]> wrote: > My guess is that the two different facilities payment.service and > payment.client are not both used from each application. > > Guessing that in the site startup code you'll find the usage of > "payment.client", and in the windows service startup code you'll see the use > of "payment.service". > > -- > 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]<rhino-tools-dev%[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.
