Well, I just saw a 34 megabyte DataInsert whose last hop was on my laptop
(behind a firewall -- for all the good that does), and whose size was larger
than
the cache size on either of my machines, *and* which was still coming in. Fat
lot of good that's going to do anyone.
So I recommend a couple of things:
Thing 1: InsertRequest messages need an InsertDataLength field. Nodes can be
configured
to reject InsertRequest messages if the size of the data is too big. This
doesn't help
with DataRequest messages, but it's a start.
Thing 2: The data store needs a maximumItemSize parameter; a data store will
not even bother trying to store a document that exceeds this.
Thing 3: We need to come to an agreement on the partial message format so
that I can implement it. I've been sketching out a proposal -- here's the
current
draft:
Properties for the "message/partial" MIME type
I have attempted to follow RFC2046
regarding this format as much as
possible.
partial.number
Identifies which part this is. Required.
partial.total
The total number of parts. Required.
partial.part<n>.key
The (hashed) key identifying part <n>.
Required in the first part, suggested in all
parts.
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
