I am going to have a UDP file transfer system for Socket Peer API's to use.

I have already explained this algo in a previous post:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=M...
0033%24NH2.15577%40sccrnsc01&rnum=5&prev=/groups%3Fq%3D%2BUDP%2Bgroup:alt.w i
nsock.programming%2Bauthor:SenderX%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUT F
-8%26selm%3DMTvH9.230033%2524NH2.15577%2540sccrnsc01%26rnum%3D5

Read my posts in the thread.

The UDP data session, has to mixed with a TCP control session. This gives us
reliability over UDP with minimal work...

The TCP control session is in direct control of UDP data sessions.

You can use a single TCP control session to manage concurrent file
transfers.

The rough protocol would be as follows:

1. Starting a session

A client would connect to the server via. TCP.

2. Client file request

The client would send a request via. TCP.

The server would get the request, and send a response saying that UDP
packets are coming.

3. Server sending file

The server would follow the response, with UDP packets containg file data
and its offset into the file.

The server would blast the whole file there.

The server would send a request to the client asking it if it got
everything...

If the client hasn't received the entire file by the time it got the ( you
got everything ) request from the server. It sends a request asking for the
file offsets it did not get, and loops back to the start of # 3.

Your using UDP for data transfer, and TCP as a controller.

This should be faster than TCP for transferring large files...

What do you think?

--
The designer of the SMP and HyperThread friendly, AppCore library.

http://AppCore.home.attbi.com