>   When I am in implementing a P2P file upload & download
> the TCP upload always fails:

>     And I wonder to know whether the Write() method of NetworkStream
> is thread safe or not?
>     Because if it calls the following code between every Write() method
> calling,
> Thread.Sleep(500); The file can be upload successfully,

> >   When I am in implementing a P2P file upload & download
> > the TCP upload always fails:

> >     And I wonder to know whether the Write() method of NetworkStream
> > is thread safe or not?
> >     Because if it calls the following code between every Write() method
> > calling,
> > Thread.Sleep(500); The file can be upload successfully,

> Loggy -

>     I am not sure I understand why you think this would be a thread
> issue. I am assuming that the client and server code are running in
> two separate programs on two separate machines, accessing two separate
> files. This would not present a thread issue.

>     By placing the Sleep() call between the Write() and Read()
> methods, you may be masking the real problem. When you Write() 4k
> worth of data, there is no guarantee that the Read() method will
> receive all 4k at once. It can easily return after reading just a few
> bytes, leaving the rest for the next Read() call.

>     When you make the Read() wait awhile with the Sleep() call, that
> may be long enough for all 4k to be available in the buffer for the
> single Read() to scoop it all up at once. But again, that is still not
> 100% guaranteed.

>     If you send a 4k block of data, make sure the receiver received
> the entire 4k block of data before continuing with the next block.
> Hope this makes sense and helps.

> Rich Blum
> Author of "C# Network Programming" (Sybex)
> http://www.sybex.com/sybexbooks.nsf/Booklist/4176

> > > Hi, Happy new year!

> > >   When I am in implementing a P2P file upload & download
> > > the TCP upload always fails:

> > >     And I wonder to know whether the Write() method of NetworkStream
> > > is thread safe or not?
> > >     Because if it calls the following code between every Write()
method
> > > calling,
> > > Thread.Sleep(500); The file can be upload successfully,

> > Loggy -

> >     I am not sure I understand why you think this would be a thread
> > issue. I am assuming that the client and server code are running in
> > two separate programs on two separate machines, accessing two separate
> > files. This would not present a thread issue.

> >     By placing the Sleep() call between the Write() and Read()
> > methods, you may be masking the real problem. When you Write() 4k
> > worth of data, there is no guarantee that the Read() method will
> > receive all 4k at once. It can easily return after reading just a few
> > bytes, leaving the rest for the next Read() call.

> >     When you make the Read() wait awhile with the Sleep() call, that
> > may be long enough for all 4k to be available in the buffer for the
> > single Read() to scoop it all up at once. But again, that is still not
> > 100% guaranteed.

> >     If you send a 4k block of data, make sure the receiver received
> > the entire 4k block of data before continuing with the next block.
> > Hope this makes sense and helps.

> > Rich Blum
> > Author of "C# Network Programming" (Sybex)
> > http://www.sybex.com/sybexbooks.nsf/Booklist/4176

>   I want to know is there any other method that can guarantee the data
> transmission
>  between the server and client?

> Thank you!

> Loggy

> Loggy -

>     TCP will guarantee (barring any catastrophic network problems)
> that your data will arrive at the other end error-free and in the
> proper order. It is your program's job to ensure that the same number
> of bytes you send are received at the other end.

>     Whether you use synchronous or asynchronous sockets, this usually
> involves checking the data for either boundary markers or size. For a
> mass data transfer, usually its easier to just get the size of the
> data being sent, send that value to the receiver first, then allow the
> receiver to loop through the Receive() method until it's gathered all
> the data.

>     Henrik is correct. If you are writing a serious network
> application, I would recommend buying some form of network programming
> book, either mine, the Wrox "Professional .NET Network Programming"
> book, the Microsoft Press "Windows Network Programming" book, or the
> infamous Richard Stevens' "Unix Network Programming" classic. A little
> bit of TCP theory goes a long way. Good luck in your network
> programming.

> Rich Blum
> Author of "C# Network Programming" (Sybex)
> http://www.sybex.com/sybexbooks.nsf/Booklist/4176