[rabbitmq-discuss] Fwd: question on the faq

Tue Jan 6 17:22:12 GMT 2009

These steps are all from the pov of my application.  I'm assuming that  
there must be messages in both directions. If this were paper based,  
step 4 would include opening the mail and reconciling booking  
confirmations against booking orders sent out in step 2, + separate  
steps to handle timeouts, etc, which I'd expect to be in the context  
of the 'transaction'.  I could write this as a series of async  
processes, but my experience of that type of design when given to  
programmers is that I get much more complexity than I need.

Does that make sense?

Tim

On 6 Jan 2009, at 16:05, Ben Hood wrote:

>
> Tim,
>
> On Tue, Jan 6, 2009 at 2:44 PM, Tim Coote <tim 
> +rabbitmq.com at coote.org> wrote:
>> Now I'm very confused. In my mind, to book my holiday example, I  
>> need:
>> 1/ Begin transaction
>> 2/ prepare definition of what to book (cab to airport, insurance,
>> flight, hotel, etc)
>> 3/ send booking requests
>> 4/ receive and record booking confirmations
>> 5/ Commit
>
> I'm probably missing the point, but how can the entity that produces
> the booking confirmations process any requests that haven't been
> committed yet?
>
> Ben
>