It is possible to configure Broker/Client to use reliable-UDP-protocol for Topics and TCP/IP for Queues? It is possible to configure Broker/Client to use UDP multicast/multicast-protocol for Topics and TCP/IP for Queues?
In other words could application create connection with different underlying protocol dedicated for Queues and Topics and force Broker to use desired protocol for different destination types including Temporary Queues and Topics? In addition it should be possible to configure in such way that all synchronous requests from client(create connection, consumer, ect) should use reliable TCP/IP(as default) and only Publishing and Consume of the messages should be done via UDP or reliable UDP or multicast. BTW, what is the state of reliable-UDP-protocol? We need a working reliable layer on top of UDP which is capable of handling re-requests of missing packets etc. and able to push Messages to all subscribers at once but not via TCP/IP (Point to Point). Tibco like and hardware based messaging solutions. -- View this message in context: http://www.nabble.com/It-is-possible-to-configure-Broker-Client-to-use-reliable-UDP-protocol-for-Topics-and-TCP-IP-for-Queues--tp17992071p17992071.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
