I'm doing some independent research on P2P network architecture and just introduced myself to this field of technology. I have a goal of deploying web servers for use in homes. I've extracted the following which I believe are requirements for a successful implementation:
· Transport layer must be implemented as TCP. · Application layer will be over HTTP/SOAP. · Must use native TCP stack on client devices so standard browsers can read data directly from the web server. · Ideally, solution is reliable across all NAT including symmetric, but primarily targeting devices behind residential NATs (which I gather is generally full and restricted cone). · Use of relay is not an option. · Use of a signaling device is totally fine. · The NAT in front of the server will need to remain in its default configuration. It would be extremely helpful for me to know: - What general components are involved in a given solution's implementation? - What libraries/solutions would be recommended for each component? - How reliable the "solution" is (i.e. does it work 40% of the time? 80%?). I'm familiar with STUNT, but I'm under the impression it isn't that reliable. Any other techniques out there? Any help/advice is greatly appreciated! Karl
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
