|
HI
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.
While the app is based on a peer to peer type
idea there will only every be two people allowed to talk to each other at a time
so I don't think in my case this would be a problem
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...
I wouldn't have though so because the socket
would get closed...(in my case)
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...
Yup, that sounds like just what I
need. Thanks /dev. Its nice to know you occasionally have a look
around these lists :-).
Regards
Max
|
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.5.0 - Release Date: Fri 25/02/2005
_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for
subscription changes, and list archive.
