The only thing that keeps the Starbucks from running on on 2003 is the
PrepareQueues code. Everything else should work okay. I started to patch it
but then got side-tracked by using RhinoQUeues. I'd like to port it to use
RQ but haven't gotten to it yet

On Fri, Jun 19, 2009 at 12:52 PM, Simone Busoli <[email protected]>wrote:

>
> What about using the queue strategy then?
>
> 2009/6/19, Mike Nichols <[email protected]>:
> > Hi Bart
> > I think the starbucks sample wont work for MSMQ 3 because of the
> > PrepareQueues setup...it is only nice to MSMQ 4 and its use of subqueues.
> >
> > On Fri, Jun 19, 2009 at 7:29 AM, Bart Reyserhove
> > <[email protected]>wrote:
> >
> >> I have 2 questions that have totally nothing to do with each other ;-)
> >>
> >> *Question 1*
> >> I am trying to get the Starbucks sample working against MSMQ 3 but it
> does
> >> not seem to work out. The replies to the customer that he has to pay do
> >> not
> >> work for example.
> >>
> >> Are there issues that I have to pay attention to to get it working?
> >>
> >> *Question 2*
> >> I need to build a system that allows users to start several workflows
> that
> >> have things in common but still are different. Of course they want 1
> task
> >> list that deals with the different workflows. I was thinking of using
> >> sagas
> >> but I am still a bit puzzled on the task list. Would it be possible to
> >> have
> >> some kind of base "state" and let all sagas use implementations of that
> >> base
> >> state class, and then base my tasklist on the base state class.**
> >>
> >> Bart
> >>
> >> >
> >>
> >
> > >
> >
>
> --
> Inviato dal mio dispositivo mobile
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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