Re: [msvc] UDP 1 last question

[/dev/null]

Does your app only communicate with one client? Yes, its based on a peer to peer idea.  I've been using the term server more or less to mean the application that starts by listening for incoming UDP data. Then using connect will shoot you in the foot because your sends can only go to one client according to that documentation you posted.  So I wouldn't use that method.   After that client hangs up, will another client connect? Yes another client may connect, depending if user wants to. Again, wonder if the connect wouldn't cause a problem with the next client... Thanks for your advice on this /dev.  Since the project works in terms of sending VoIP data across a UDP connection I think I will leave it alone.  Now I've only got to figure out how to detect when the line is dropped.... You can have the client send an "I'm still listening" udp packet every 10 seconds or so.  If the server hasn't received such a packet in say 30 seconds, quit transmitting to that client.  Likewise you can have a whole range of client commands like [ "restart", "fast forward", and "rewind" (if this is a recorded message) ], "I'm disconnecting", etc...   /dev

_______________________________________________
msvc mailing list
msvc@beginthread.com
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for 
subscription changes, and list archive.