I agree. It would be better to do like the transport, have an object attached
to the node with newAddress(String protocol, String address) and
newConnection(String protocol, Address addr).
I have a question for somebody: If how the node communicates is the protocol,
and if the format of the messages is the transport, then what should the
underlying protocol used ("tcp", but could be anything) to it be called?
On Sat, 13 May 2000, Ian Clarke wrote:
> > Hmmm, I notice that the tbAddress class is creating a dependancy with
> > the testbed package - does this have to be in the Freenet.* package,
> > surely it belongs in Freenet.testbed.*?
>
> Ah, with a small amount of thought I have realised why it is in here
> (duh).
>
> Perhaps this suggests an alternative approach might be appropriate for
> the loading of different types of Address and Connection. It is not
> like we add new types with sufficient frequency to justify this "plugin"
> capability.
>
> Ian.
>
> _______________________________________________
> Freenet-dev mailing list
> Freenet-dev at lists.sourceforge.net
> http://lists.sourceforge.net/mailman/listinfo/freenet-dev
--
Oskar Sandberg
md98-osa at nada.kth.se
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
