Re: Winsocket send fails
- From: "Mandi" <mandi@xxxxxxxxxxxx>
- Date: Thu, 27 Dec 2007 20:51:23 +0200
Thanks Mr. Shcherbyna,
Unfortunately, so far I advanced just a little with the problem...
Some more details about the environment-
The server is an encoder that I develop that streams multimedia to a client
(Windows Media Player) with tcp across the Internet. If the baud rate is
low - say 50kb/s it works fine. If the client is on the same LAN it works
fine either. If the baud rate is high, say 70kb/s and above it breaks just
when it starts with "WINSOCK ERROR--SERVER: Send error 10053".
Trying to stream with a professional application like Windows Media Encoder
to the same Player across the Internet works fine.
Does this information helps something in searching the problem?
Regards
Mandi
"Volodymyr Shcherbyna" <v_scherbina@xxxxxxxxxxxxxxx> wrote in message
news:uSBRg84RIHA.4128@xxxxxxxxxxxxxxxxxxxxxxx
In case of synchronous I/O you can use select(...) function to check
socket for errors.
--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx
"Mandi" <mandi@xxxxxxxxxxxx> wrote in message
news:ebQlnyxRIHA.4180@xxxxxxxxxxxxxxxxxxxxxxx
I use Winsocket send but the function fails from time to time. The error
message says that its a Winsock send error, but I can't debug it farther.
Is there some api that I can use, before using the send, that exposes the
socket status, or can help in some other way?
Regards
Mandi
.
- Follow-Ups:
- Re: Winsocket send fails
- From: Alexander Nickolov
- Re: Winsocket send fails
- References:
- Winsocket send fails
- From: Mandi
- Re: Winsocket send fails
- From: Volodymyr Shcherbyna
- Winsocket send fails
- Prev by Date: Re: Flow Control In UDP/TCP
- Next by Date: Re: Winsocket send fails
- Previous by thread: Re: Winsocket send fails
- Next by thread: Re: Winsocket send fails
- Index(es):
Relevant Pages
|