Remote Non-tx Queues and Local tx queues

[Travis]

MT seems to assume that all remote queues are tx and local queues are
not. When you have different pieces of MT living on different machines
that gets in the way.

http://groups.google.com/group/masstransit-discuss/web/transactional_identifier_in_uri_string.patch

This patch allows you identify a queue as transactional or non-
transactional via the query string: ?tx=true or ?tx=false. The
MsmqEndpointAddress now understands that there's a query string and I
also included a couple tests for it.

The default is still in place (remove = tx; local = non-tx).

-Travis

[Travis Smith]

Correction:

The default is still in place (remote = tx; local = non-tx).

[PhatBoyG]

Still dealing with unit test fallout for this patch, but should have
it applied soon once I finish testing with the reference apps.

On Nov 4, 3:27 pm, Travis Smith <tra...@legomaster.net> wrote:
> Correction:
>
> The default is still in place (remote = tx; local = non-tx).
>
>
>
> On Wed, Nov 4, 2009 at 3:23 PM, Travis <tra...@legomaster.net> wrote:
>
> > MT seems to assume that all remote queues are tx and local queues are
> > not. When you have different pieces of MT living on different machines
> > that gets in the way.
>

> >http://groups.google.com/group/masstransit-discuss/web/transactional_...

[PhatBoyG]

Pretty sure this is solid now.