For 1), take a look at MQTT. It's probably the most compact protocol and its main claim to fame is low-bandwith/limited device pub/sub.
On Thu, Feb 28, 2013 at 1:41 AM, jan <jan_decoo...@yahoo.com> wrote: > Hi, > > I am working on a project where we have one central J2EE core application > which sends out messages to approx. 500 client computers (using JMS). These > client computers have 4 network interfaces. The basic idea is that certain > services are routed on specific network interfaces. One network interface > on > those client machines is a M2M-network (mobile) which is a dedicated > channel > for messaging. I currently face two problems: > > 1) I need to find the "least traffic generating" protocol to send messages. > We pay the mobile connection for every byte we send, thus we need to keep > the traffic as low as possible. What do you recommend: TCP, UDP > (Websockets?)? > > 2) Since I have 4 network-cards and interfaces I need to bind the > AMQ-client > to a specific interface. The client may only receive messages f.e. on > "eth3" > or whatever. The selection of the network interface depends on a > configuration file. When the client sends back a messages, it should also > be > routed on this interface. I want to avoid routing with iptables. Is there a > solution? > > The project is still very flexible and I could switch the strategy very > easily as long as ActiveMQ is involved. > > Thanks & Greetings > Jan > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Best-protocol-network-interface-binding-tp4664240.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
