Do I need to choose a different port or does the system do that
automatically?
I would assume I need to configure it, otherwise I will not know what
port to send to.

What is the format of the uri to include the port number?

On Aug 5, 12:15 pm, Mike Nichols <[email protected]> wrote:
> The win service will configure a bus on a different port...otherwise you
> will get socket protocol errors. To send messages to the win service from
> the web app you can specify the endpoint directly or you can configure the
> messages you are sending there by their namespace in the config.
>
> On Wed, Aug 5, 2009 at 8:52 AM, Jason Meckley <[email protected]>wrote:
>
>
>
> > I currently have a web application utilizing RSB & RQ. all is working,
> > however we discovered an issue where no activity (user input) means no
> > calculations. over the period of days data is not calculated.
>
> > Resolution: Create a windows service to run daily that runs the
> > calculations every day. Should be simple enough, however I do not seem
> > to understand the semantics of RSB and RQ to get this working
> > properly. Up until now my use of RSB has been contained within a
> > single project deployment. Now I need to communicate across projects
> > (web to service).
>
> > Here are my thoughts:
> > 1. Web will update database directly with user input then send a
> > message to start a specific calculation.
> > 2. Service will receive the message and process.
> > 3. Using a timer the service will also calculate all calculations in
> > the early morning hours.
> > 4. The web does not need to be concerned with receiving a reply from
> > the windows service (fire and forget).
>
> > Questions:
> > 1. Do I need to start the bus for both the windows service and the
> > website, or can I just start the bus on the windows service? It
> > appears I need to start it on both, why is that?
> > 2. Can I use RQ across multiple projects/deployments on the same box?
> > 3. Using RQ and staring the service in both applications would create
> > the message databases in directories of both the web and windows
> > service. How would this work with sending messages to the proper queue
> > to be processed? it seems they would operate independently of one
> > another.
> > 4. Because the services will be hosted on the same server would the RQ
> > Uri's be the same? here is my current configuration for both
> > applications
> > ----------------------------------------------------------------
> > <facility id="bus for windows service">
> >        <bus
> >                name="XYZ"
> >                threadCount="3"
> >                numberOfRetries="5"
> >                endpoint="rhino.queues://localhost/xyz" />
> >        <messages>
> >                <add
> >                        name="xyz.Messages"
> >                        endpoint="rhino.queues://localhost/xyz" />
> >        </messages>
> > </facility>
> > ----------------------------------------------------------------
> > <facility id="bus for website">
> >        <bus
> >                name="XYZ"
> >                threadCount="3"
> >                numberOfRetries="5"
> >                endpoint="rhino.queues://localhost/xyz" />
> >        <messages>
> >                <add
> >                        name="xyz.Messages"
> >                        endpoint="rhino.queues://localhost/xyz" />
> >        </messages>
> > </facility>
> > ----------------------------------------------------------------
> > is this correct? if not what changes do I need to make?
> > 5. should I change 'localhost' to the actual host name for testing or
> > deployment?
> > 6. is there anything else I should know about my setup (good/bad/
> > problematic)?
>
> > thank you in advance
--~--~---------~--~----~------------~-------~--~----~
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