…hem in storage
…bQueueStrategy. Ran into an issue where messages were being sent out at the wrong time and found a thread on the Rhino Tools Dev Google Group page (http://groups.google.com/group/rhino-tools-dev/browse_thread/thread/da31001be7e7ad65/445773b1225b881b?q=#445773b1225b881b) where someone ran into the same issue and proposed a fix. I implemented the changes he mentioned and added an extra check to the "if (message == null)" check that only yields a new TimeoutInfo if the message's extension is longer than 16. If the extension is shorter than 16, the BitConverter statement fails. Wrote a couple of tests to make sure the problem was fixed.
Fixing the non transactional queue support for remote queues. Will now create sibling queues with the same transactionability as their eldest
… or non transactional
when using flat queue strategy
in a service mode, this allows Windows to add the error to the error log
…t out of subscriptions and would require either explicitly subscribing, or not using subscriptions altogether.
Not having this breaks the DelaySend infrastructure... Messages would be delay sent, but then if the app is restarted they would be left in the void
…revent build errors.