search

Esri / vehicle-commander-java

The Vehicle Commander template demonstrates best practices for building in-vehicle military applications with ArcGIS Runtime. The Vehicle Commander template contains source code for an in-vehicle application.
Apache License 2.0
16 stars 12 forks source link

Send unicast and/or multicast messages, especially for GeoEvent Processor #20

Open garysheppardjr opened 10 years ago

garysheppardjr commented 10 years ago

Vehicle Commander sends UDP broadcast messages. These messages only go as far as the router to which the device is connected. That often means the machine running GeoEvent Processor does not receive these messages.

I propose adding unicast and/or multicast messages, in order to get past the router to GeoEvent Processor. GeoEvent Processor has a connector ("Receive text from a UDP Socket") that can be configured to handle either broadcast/unicast (port only) or multicast (address and port).

conklinbd commented 10 years ago

It is my understanding that many routers will block UDP traffic even if they are multicast. I suggest we add a TCP method. We can set up an input connector for Geomessage on a TCP socket.

pHill5136 commented 10 years ago

I think we already have a connector for this -- geomessage over tcp. I made one before we updated to 10.2.1. It may have gotten lost during the upgrade. If it is still there, it will be one of the choices for creating an input service in ges. I am in our nga showcase event here in St. Louis today. I will check either later today or tomorrow, when I get a chance.

-Patrick

From: Ben Conklin [notifications@github.com] Sent: Wednesday, December 04, 2013 5:45 AM To: Esri/vehicle-commander Subject: Re: [vehicle-commander] Send unicast and/or multicast messages, especially for GeoEvent Processor (#20)

It is my understanding that many routers will block UDP traffic even if they are multicast. I suggest we add a TCP method. We can set up an input connector for Geomessage on a TCP socket.

— Reply to this email directly or view it on GitHubhttps://github.com/Esri/vehicle-commander/issues/20#issuecomment-29805339.

csmoore commented 10 years ago

Unfortunately, Http/s(Port 80, 443) is the only way to guarantee that a router's security settings won't filter you-this is why REST, SOAP, WCF, etc. are typically used. And this is why you sometimes have to log into your home router to open other ports/protocols for some network stuff (like XBox, etc.).

So you just may want to test with the existing TCP/IP csv simulator that comes with GEP beforehand just to confirm that it will work OK with your particular network setup.

For the Geomessage Adaptor, I think you can create a connector with any Transport for this, UDP, TCP, even the JSON Folder watcher (which will work with any file type, not just JSON), and it should work.

jrweakland commented 9 years ago

Added to backlog - https://app.asana.com/0/23019535413946/23267996678693