Seems like the primary difference between the SubQueueStrategy and
FlatQueueStrategy implementations is the usage of a the semicolon or
pound symbol to delimit the QueueUri and SubQueue in the QueuePath.
If this is the case, might it make sense to update all the hardcoded
delimiters to provide a more abstract implementation?
The reason I ask is that lines of code like _PrepareQueues.Prepare
("msmq://localhost/starbucks.barista");_ in the Starbucks.Tests
project are failing due to the hardcoded semicolon in the
PurgeSubqueue method. And there are quite a few other hadcoded
subqueue delimiters in the Rhino.ServiceBus.Tests project that fail
with MSMQ 3.0. It seems like this is an easy fix, but wiithout having
access to an MSMQ 4.0 machine right now, I'd have a hard time
verifying that it works for both strategies.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
