From: Leon T. <fa...@gm...> - 2010-07-12 00:53:59
|
On Fri, Jul 9, 2010 at 1:47 PM, Radim Kolar <hs...@se...> wrote: > Dne 2.7.2010 18:20, Jeff Hawkins napsal(a): > > FSPv3 was not supposed to be just FSPv2 over DTLS but protocol with new > protocol header with for example 8 byte wide file offset pointers. More > detailed list of requirements for FSPv3 needs to be made first and then > write draft specification of this new protocol. FSPv3 design must be > done in more strategic way than just accept some code changes. Existing > FSPv2 users needs to be contacted if they are interested in design of > FSPv3 and then submit their requirements for such new protocol. For > example - should be FSPv3 still windowless protocol? > Personally, I am in favor of making FSPv3. IMHO it should have * More structured ways of querying the server's capabilities and settings. Useful for many other things on my list. * Proper error codes obviously. * (Auto-)negotiation of retry times. The current protocol is optimized for low-loss high-latency circumstances. It could for example perform much better on low-latency high-loss wireless networks by retrying much sooner. * Windows: this can improve speed without much costing that much in state. Throttling can be achieved using more conventional and flexible mechanisms too. It should probably be negotiable between client and server. * Support for more than one connection per IP address. This might also be negotiable between client and server. * Large file support: in 2010 this may be the biggest disadvantage of FSP. Can't use it to distribute big files. * Better authentication and authorization. Cleartext passwords don't add that much security. * Optionally support encryption. Preferably through DTLS. * Reduction of the number of packets sent by compounding them when possible. I'm willing to help with specifying and prototyping. Leon |