BTW: In some situations we just want to fire and forget messages to notify running UIs, we assume we don't need a queuing system in this context, because we want the UI to get notified if it's running and subscribed to the message it needs. Is it possible to publish/send messages without queuing? I mean, is there a way to implement a bus message so when it's sent, it is sent over the wire but not persisted in the queuing system?
Thanks. On Feb 1, 2:20 pm, Jason Meckley <jasonmeck...@gmail.com> wrote: > Queues: MSMQ, Rhino.Queues, your own implementation for another type of > queue > Transactional: yes all messages are processed within a transaction. I > believe you have the option to disable transactions for the MSMQ. > Transactions with an isolation level of Serializable is used by default. > Benchmarks: check out Ayende's blog, I believe he has some comparisons of > Rhino.Queues vs. MSMQ > Limitations: no critical limitations. The only down side to Rhino.Queues is > that you can view what's going on in the queue like you can with MSMQ. But > given the benefits of Rhino.Queues this is trivial, depending on the > context. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
