I'm just going to reply to all the comments at once -- maybe I can
reassemble the thread this way. (-:
Ian Clarke writes:
> 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...
We should probably ensure this mechanism can be generalized to
include redirection, and possibly different methods for splitting
the data.
Redirection is a different MIME type (multipart/external-body, as
I recall). Sticking to the existing format would be a "nice" idea
(although clearly not necessary).
As for data-splitting methods, I was thinking there should be some other
property of the message type (property name undetermined), that, when
present, signifies how the message should be reassembled.
1723 writes:
Bill Trost schrieb:
> 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.
but what will happen if _all_ neighbour-nodes reject the document?
Then your message is too big, and you need to break it up.
> Thing 2: The data store needs a maximumItemSize parameter; a data
> store will not even bother trying to store a document that exceeds
> this.
i'd say, as long as the datas doesn't exceed the diskCache, the
separate documents may have any size.
Then you don't set the maximumItemSize parameter. (-:
Brandon writes:
> Thing 1: InsertRequest messages need an InsertDataLength field...
The DataSend will resend to another node on a RequestFailed. Just
send a RequestFailed if the DataLength in the DataSend is
unacceptable to you.
On insert?? The sender isn't expecting any sort of response when the
data is being inserted.
> Thing 3: We need to come to an agreement on the partial message
> format...
> Properties for the "message/partial" MIME type
I don't like partial as the name. Perhaps multipart?
"Message/partial" is the term in the MIME specification. Multipart is
referred to messages that have, well, multiple parts -- the dual of a
message that is in multiple parts, and each Freenet message *partial*ly
contains the document.
This is probably at the bottom of the pile of things to get excited
about. The user's won't even see it.
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
