> 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.
What situations are these? There may be an elegant way to reforumlate the problem so that this solution will still work without losing fuctionality. For instance, in the case of replies, they can have a new unique id and put the old unique id in the OriginalID field. That way dropping loopbacks is a Message problem and routing replies is still a Reply problem. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
