LabVIEW Web Services

[ADL]

I am trying to figure out whether LabVIEW Web Services uses TCP/IP or UDP.

We are serving up a web service, and all the data is being sent, but sometimes all the packets do not arrive at the other end.  The client requesting from the service doesn't know what to do.

Does anybody have an idea if this is a UDP problem, a setting issue, or should the client have to deal with lost packets, as opposed to the TCP/IP dealing with that.

If anybody has an idea on this, I would love to hear it.

A. 

[nathand]

The web uses HTTP (HyperText Transfer Protocol) to request and receive data, and is built on TCP.  That's the protocol used by web services (if it used some other protocol it wouldn't be a web service).  There's no use of UDP.  How do you know that the data is being sent but not received?

[ADL]

We are sniffing the packets at the output from the server, and they are all present.

We then sniff again at the client, and they don't always all arrive, i.e. sometimes packets are missing.

There is no rebroadcast however, the software on both ends just stop communicating? thoughts?

We haven't built in any smarts to the client software to deal with lost packets, as we believed that TCP/IP would take care of this.

Helpful ideas/thoughts/pointers would be appreciated. 

A. 

[nathand]

If you're sniffing packets you should be able to determine whether they're TCP or UDP...

I don't have any good ideas, I've never seen packet loss except due to a broken cable.  What's between the client and the server?  Can you put both applications on the same machine and verify that all data is received?  Connect them directly (with a crossover cable or hub) and check for the same behavior?  Do other applications communicating between the same two machines also have problems?