Re: Network Stream behaving strangely.
From: C# Learner (csharp_at_learner.here)
Date: 03/22/04
- Next message: Lee Alexander: "Re: How to deal with default case"
- Previous message: Simon Harvey: "Method or property?"
- In reply to: Ofer Achler: "Re: Network Stream behaving strangely."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 09:20:00 +0000
Ofer Achler wrote:
> C# Learner wrote:
>
> It worked! thank you!! I was soo frustrated!!!
Great :-)
>> A problem with your code is that it isn't able to handle the fact that
>> a Read() attempt might return less data than you're asking it for.
>> This /could/ cause your issue as stated above.
>
> It has, it has!! i thought the packet size issue would be resolved
> because i can specify how much the stream can read, apperantly, thats
> not true =)
I believe this can happen due to the nature of TCP/IP.
On http://floppsie.comp.glam.ac.uk/Glamorgan/gaius/security/5tcpip.html
it reads:
12. Fragmentation and reassembly
* IP datagrams may be fragmented en route
o if intermediate nodes cannot cope with a large datagram (MTU
(maximum transmission unit) is smaller than datagram size)
* IP datagrams may be reassembled en route
o although not a good idea as routing is dynamic. (So datagrams may
not always travel the same route)
> [...]
>
> I took this code and modified it a little (it doesn't quite work as it
> is) and am planning to release it in a GPL program, i assume that's ok.
Sure, no problem.
> [...]
>
> Thanks, youve been a good helpl :)
No problem -- I'm glad it helped :-)
- Next message: Lee Alexander: "Re: How to deal with default case"
- Previous message: Simon Harvey: "Method or property?"
- In reply to: Ofer Achler: "Re: Network Stream behaving strangely."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
