Brett Henderson wrote:
(b) Encoders/Decoders that actually work by passing thier content through streaming to manage larger amounts of data efficently. Data for which the length is probibly already known (Files). An interface which supports handing objects and Streams manages this:
Can you give some examples of algorithms where the length needs to be known in advance?
My code may break horribly with such an algorithm :-(
I'm speaking specifically about multipart encoded request/responses in http and smtp. And not specifically that the encoding algorithm (which is just a bunch of "wrappers" and "boundaries") needs to now the length previously, just that its standard to set a length header in the request or response proir to sending out the content (thus total length of the content needs to be known prior).
I now do not think it has very much to do with the Streaming Codec ideas your focusing on (while they are still quite valuable in their own right).
-Mark
-- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
