> What possible use is there for this "streaming" complication that > can't be done with a continuing series of discrete, finite fetches? > Perhaps with each frame of a stream containing the key of the next > frame? This is a major complication, and if there's no use for it > that can't already be done with the system as it is, why mess with > it at all?
I would say that implementing streaming over discrete finite fetches is more messy and complicated than adding a little to support streaming. I think the protocol is being overly geared towards fetching static content. We should make a generalized protocol which can handle either dynamic or static content and then have more specific messages to handle the two types. It's really quite easy to allow for streaming in terms of the protocol. We just make DataLength a part of DataSend and DataInsert instead of Message. That way messages that deal with static content can have a length restriction and messages that use streaming content can not worry about it. That's it in terms of the basic protocol. We might need a couple of messages to handle streaming content. Doing streaming data with discrete fetches is a bad idea because then you have 2 messages per unit instead of 2 messages for the entire transaction. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
