But you can't just toss out a message on the grounds of having a MessageMemory for it. There are plenty of situations where it is ok to have a message return, it depends completely on the implementation of any particular message.
Oskar Sandberg - mail/finger md98-osa at nada.kth.se - Crypto is a human right On Thu, 13 Apr 2000, Brandon wrote: > > > Which would be why the received method in Message.java is final. Yes, it is > > possible all implementors won't be that careful, but it is extremely easy to > > make sure that the HTL is decremented once and for all. > > We can abstract away loopback detection similarly. We only need to see if > the UniqueID of the message is the same as one in the MessageMemory. It > can go in Message and be a final method. That puts loopback detection on > the same level of code maintenance as HTL decrementing. > > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
