Re: Asynchronous sockets and buffer size
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Mon, 28 May 2007 11:17:42 -0700
On Mon, 28 May 2007 03:45:21 -0700, Matthew Geyer <nospam@xxxxxxxxxxxxxxxxxxxx> wrote:
[...]
thank you both (Peter & Michael) for helping me, and especially Peter for pointing out the Socket.EndSend bug that i probably never would have noticed.
You're most welcome...glad to hear it's all working now.
kind of embarrassed i had issues with such simple stuff, this time i'll blame the tonsilitis + fever i'm experiencing ;)
No need to be embarassed, especially if you're relatively new to the socket API. It's a simple enough API, but there are some subtle implied behaviors that unless you've read every single word in the documentation (and I admit, most people don't) you wouldn't know about. Once you've done it enough, it will become second-nature to notice those things. :)
Pete
.
- Follow-Ups:
- Re: Asynchronous sockets and buffer size
- From: Michael Rubinstein
- Re: Asynchronous sockets and buffer size
- References:
- Asynchronous sockets and buffer size
- From: Matthew Geyer
- Re: Asynchronous sockets and buffer size
- From: Michael Rubinstein
- Re: Asynchronous sockets and buffer size
- From: Matthew Geyer
- Re: Asynchronous sockets and buffer size
- From: Peter Duniho
- Re: Asynchronous sockets and buffer size
- From: Matthew Geyer
- Re: Asynchronous sockets and buffer size
- From: Peter Duniho
- Re: Asynchronous sockets and buffer size
- From: Matthew Geyer
- Asynchronous sockets and buffer size
- Prev by Date: Re: wierd exception
- Next by Date: Re: Want form to show changing data. But it could be closed, or closing, during update.
- Previous by thread: Re: Asynchronous sockets and buffer size
- Next by thread: Re: Asynchronous sockets and buffer size
- Index(es):
Relevant Pages
|