i know that it doesn't guarantee data delivery and is's based on tcp/ip. i'd like to know exact differences between communication with tcp/ip and datasocket.
Datasocket uses TCP/IP, but is (especially on recent LabVIEW versions) much more easy and intuitive to use. You don't have to worry about connection opening/closing, ports, and all the other details of a raw TCP/IP communications. NI has already done all the hard work.
Have a look at some of the examples included with LabVIEW.
DataSocket will lose your data. TCP/IP won't. Stick to TCP, trust me.
Jon
"danielk" wrote in message news:506500000008000000CC900000-1042324653000@exchange.ni.com... > i know that it doesn't guarantee data delivery and is's based on > tcp/ip. i'd like to know exact differences between communication with > tcp/ip and datasocket.
i thought i'll get more specific inforamtions. i'd like to know differencies between transmission with tcp and datasocket in particular layers (application, transport, network)