New topic: 

Sniffing a Local Network

<http://forums.realsoftware.com/viewtopic.php?t=34373>

         Page 1 of 1
   [ 1 post ]                 Previous topic | Next topic          Author  
Message        Jason_Adams          Post subject: Sniffing a Local 
NetworkPosted: Wed Jun 23, 2010 8:06 pm                         
Joined: Fri Nov 10, 2006 4:10 pm
Posts: 545                Really, I have two questions rolled in one, so bare 
with me if you will:

My program is connecting to a PLC acting as a server. The app receives data as 
the PLC runs a machine and stores it to a CSV. At times I may receive packets 
as fast as 1/250ms. This will always happen over a local network. I understand 
that TCP is more secure than UDP, and it is important that the data received is 
accurate. But is the overhead of TCP too much to permit the speed I'm hoping 
for? Which protocol would be recommended?For various reasons, the addressing is 
going to be dynamic. As such I was going to have the app broadcast a packet 
recognized by the PLC, then have the PLC respond—and make the connection. 
Problem is, I'm not sure how to do this; don't I need to first make a 
connection to a server before writing to it? I believe UDP is a connectionless 
protocol, so would I first broadcast via UDP, then thereafter make a TCP 
connection? Inconvenience here being I would also have to set up a UDP server 
on the PLC.
As always, the advice is greatly appreciated. Thanks!      
_________________
Vista Home Premium
RB Pro 2009r3

"Christianity has not been tried and found wanting; it has been found difficult 
and not tried." - G.K. Chesterton  
                             Top            Display posts from previous: All 
posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost 
timeSubject AscendingDescending          Page 1 of 1
   [ 1 post ]      
-- 
Over 1500 classes with 29000 functions in one REALbasic plug-in collection. 
The Monkeybread Software Realbasic Plugin v9.3. 
http://www.monkeybreadsoftware.de/realbasic/plugins.shtml

[email protected]

Reply via email to