Not sure I have followed the whole scenario through, but the camel-mina and camel-netty components can help you interface with external systems via TCP. These components allow Camel to participate either as a consumer or as a producer of data.
Whether the server will pull the data from the device, or whether the pattern is a push one, will highly depend on your actual requirements and the choreography of the system you want to achieve, as well as your network setup. There is a number of architectural and functional decisions you need to make beforehand. Having said that, Willem's point is quite good. If the server initiates the connection and polls each device, does the server know in advance the IP address of each digi device? Are they static? Otherwise, in your overall choreography you could consider a "check-in" pattern by which each digi device will connect to the server when it comes online or when it's IP address changes, reporting its own IP address so that it can be contacted later on. Regards, Raúl. On 14/11/2011 21:25, "newbiee" <[email protected]> wrote: >I will be opening a socket connection with digi device some thing like >this: > >Socket clientSocket = new Socket(IP address, port#); > >my application is going to act as a client sending commands to the digi >device. Digi device in return will send my application a message that my >application will put in the queue for further processing. > >Once data is in the queue I can route it using CAMEL, I understand that. > >What I am trying to find the how MINA component for CAMEL can be used in >communicating with digi device and what is its significace. Please >explain. > >The example that I have tried and mention above is good only if my >application is a server but this is not the case, since I have to open the >socket connection. > > > >-- >View this message in context: >http://camel.465427.n5.nabble.com/Remotely-pulling-messages-using-CAMEL-tp >4971149p4992507.html >Sent from the Camel - Users mailing list archive at Nabble.com.
