No harm, but also no point in setting up a queue and a receiving
thread if it's not going to receive anything.
Case: web frontent or a web service receiving data in http requests
and sending it to some backend windows service for further processing.
The web frontent has no state and is not interested in getting any
responses for the messages it sends.
Sacrificing a thread and a queue is not a big problem, though, so I
won't be solving it for now.
R



On Oct 8, 4:35 pm, Jason Meckley <[email protected]> wrote:
> what harm is there in setting up the receiving queue? it's a one time
> operation and is handled automatically by the framework.
>
> On Oct 8, 8:17 am, Ayende Rahien <[email protected]> wrote:
>
>
>
> > Not right now, no.You could patch it to do so, though
>
> > On Thu, Oct 8, 2009 at 1:27 PM, nightwatch77 
> > <[email protected]>wrote:
>
> > > Hi, is it possible to set up RSB without receive queue for application
> > > that will only send messages and never receive? I mean the queue would
> > > be 'shared' with the receiving application.
> > > R
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to