On Fri, Dec 18, 2009 at 08:20:47AM +1300, Jason Haar wrote: > On 12/18/2009 05:31 AM, Marc Perkel wrote: > > > > In this case the idea is to gather data in real time. So those who > > gather data need to be able to send the data to a central place that > > receives the data and then makes it available to everyone. > > > You've lost me there - DNS would allow you to do that. You run the DNS > server, SA does the queries, they get routed through the standard DNS > hierarchy, you get to see them (and respond), interpret and make that > data available via any mechanism you want - probably also via (a > different?) DNS. A short TTL would reduce lost data (in fact, the only > possible cached-caused data loss would be for duplicate queries from the > same SA instance)
Ok, while DNS would "allow" that, it would be a real waste of a protocol. Why would you want to make the sending party wait for a response that only adds delays and has no purpose? Simply send a UDP packet and be done with it. No TCP or DNS overhead. One or two lines of perl.
