great. i think i will use MINA for the protocol/public-facing, since it will be a custom protocol, and ActiveMQ to shuffle the data in the background. i heard there was some talk of combining MINA and ActiveMQ, seeing that their functionality overlaps quite a bit. that might be a good step in the future, if the core dev's see an opportunity there (= anyway, thanks a ton pete for all your help..
- Austin On 7/11/06, peter royal <[EMAIL PROTECTED]> wrote:
On Jul 8, 2006, at 5:45 PM, Austin Lee wrote: > My program would be ignorant to the queue's transport > (VM or socket) which seems quite convenient. MINA also has a VM transport as well. > What do you think of ActiveMQ's NIO ability to handle multiple > connections? How does it stand up against MINA? Might be a question best to ask the ActiveMQ folk. > Would a hybrid setup with ActiveMQ to provide the queue/transport > between servers and MINA > to provide the public-facing side be the best approach? depends on what you need.. MINA is really a protocol toolkit.. no reason that ActiveMQ couldn't use MINA underneath for its NIO needs. So, if you want NIO and ActiveMQ can do that with the protocol that you want, no reason not to use it directly. But you certainly could put MINA in front, especially if you wanted to munge the data to/from your own protocol. -pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
