Thanks for your suggestion. I think I understand why you go for stomp and mqtt. Stomp being text oriented will be easy to trace and read. Mqtt has its origin in m2m communication and is ideally suited for low bandwidth lines with perhaps not ideal quality. And both are for example supported by ActiveMQ. Am I correct with my interpretation ? What I don't fully understand is why you suggest websockets. Perhaps I should have mentioned that the hundred machines don't run browsers but use standalone java applications. Or is there something I don't see that made you suggest websockets ? Perhaps I should learn more about remoting but do you know whether this all will work out with remoting ? When I say "remoting" I mean having code that get's called by using a stub which transparently uses xmpp/stomp/amqp/mqtt/whatever to send the request to the hundreds of machines.
Gesendet: Dienstag, 19. November 2013 um 16:59 Uhr Von: "Christian Posta" <christian.po...@gmail.com> An: "users@camel.apache.org" <users@camel.apache.org> Betreff: Re: Efficient transport for remoting behind firewall ? or stomp/mqtt over websockets?
