Transport protocols and bulk file transfer

["Jeff W. Boote" <>]

I have a few comments with regard to the API.

I believe it is appropriate to make the CC algorithm (protocol) a run-time 
selection. The reason is simply that there are most likely some applications 
where you would want to use a different set of trade-off's for different sockets 
within the same executable. If you make these things compile-time configurations 
then it is difficult to use multiple "protocols" within the same application at 
the same time.

The API is currently missing tuning parameters. I suspect the easiest thing is 
to make a single sockopt that specifies the "protocol" as well as all the tuning 
parameters for that given protocol with a single structure. This could then be 
the way the protocol is selected at runtime as well. Each protocol could define 
the structure needed for the given set of tuning parameters, and the structure 
could have a header section for the things that are common across all protocols. 
(The protocol "type" is the only thing I can think of off the top of my head 
here, but implementing the API may expose others.)

The last piece that would be needed is a way to specify the "default" protocol 
structure to be used if the sockopt is not selected. I would either provide an 
access function to specify it, or use a global variable. I would have a small 
preference toward the function just because it would make it easier to make 
additional language bindings more symmetric.

jeff