Comment 8 for bug 843268

Revision history for this message
Mike Mestnik (cheako) wrote :

I have experience with network coding and am able to write code to talk to both Socks(several variants) and HTTP Proxy servers. Are there any others?

What troubles me is the decision tree that should be called every time a connection is requested. This Tree needs to include a state-full matrix for current connection status/location. There also needs to be a handful of optional arguments an application can pass for indicating many attributes of a connection. I'll attempt to list a few and try and highlight the ones that matter.

(UDP/TCP/SCTP 4/6/46/64) 46 is ip4 then ip6 and 64 is ip6 then ip4 note this effects DNS lookups, perhaps such that the system resolver is inadequate. Thus DNS servers and resolution should be part of each Network Profile.

Application Level Protocol * HTTP/FTP/SSH/CIFS...
Application(Presentation Level) * ncftp/lftp/wget/axel
Account *
Session (Optional?)