Schwab,Wilhelm K wrote:
Philippe,
I've never had much use for UDP, but the common things should work the same, at least to a point.
UDP is cool.
UDP is the protocol that does not guarantee packet order or even delivery, right?
Yes, and it's packet ("datagram") oriented while TCP is stream oriented.
So anything remotely stream related is out, and there might be other things that should legitimately be different, if I'm thinking of the right thing.
Sure. That's why it's uncool to have one class for two things that are so vastly different.
While I'm displaying ignorance, there is a negotiated rate serial protocol that ends up being implemented using sockets. I can't think of the name of it but know where to look for a reminder. It is something I would like to see supported "some day."
There is the "datagrams" protocol on Socket. That's probably what you want when you're working with UDP. Then there's stuff that doesn't work when you're on UDP and gives a cryptic error message like #connectTo:port: and there is stuff that might work in both cases (#getOption, #setOption:value:). You have no idea from looking at the class what you can use in which case and what not. Cheers PHilippe