On Tue, 29 Aug 2000 21:08:06 +0700, Oskar Sandberg wrote: >UDP is an alternate transport. The current Freenet Protocol over plain UDP >will not be possible, since it assumes the transport is not lossy - >another presentation/application layer protocol would have to be used.
Yes, that's what I meant - use UDP together with an additional layer that will emulate TCP. I have hacked something like this yesterday, but it's far from working. It boils down to: An UDPServerSocket listens on an UDP port and looks for special SYN packets which initiate a new connection, and places them in a buffer. Such a connection is returned in the form of an UDPSocket as soon as the client accept()s (equivalent to TCP's backlog). The ServerSocket forwards incoming packets to their appropriate Sockets, as determined by remote host:port. ACKing is done like with TFTP: send one packet, wait for ack, repeat. When waiting times out, the packet will be resent (maximum n times). UDPSocket's have InputStream and OutputStream, so they would work like the normal Sockets. >HTTP and FTP are alternate presentation/application layer protocols. They >are not useful for Freenet, but one could imagine hiding Freenet's traffic >inside the data part HTTP and FTP traffic. Not now though. It's not like I'm busy with anything more important, so I might aswell do something simple like this :) Martin -- FemFind - SMB/FTP search engine (GPL'd) http://femfind.codefactory.de/ Other projects: http://www.codefactory.de/ _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
