On Tue, 2010-01-12 at 04:21 +0000, Martin Pool wrote:
> How would you feel about using mime multipart with separators? That
> allows streaming, has little overhead, could even allow things as
> unescaped 8bit, and will leave text readable.
Sounds fine to me as long as the programming API (addDetails,
getDetails, and the Content and ContentType API's used by the details
dict passed to outcomes) remains the same. If it needs to change I may
still be happy, but I'd want to see the changes first :)
On Tue, 2010-01-12 at 04:21 +0000, Martin Pool wrote:
> How would you feel about using mime multipart with separators? That
> allows streaming, has little overhead, could even allow things as
> unescaped 8bit, and will leave text readable.
Sounds fine to me as long as the programming API (addDetails,
getDetails, and the Content and ContentType API's used by the details
dict passed to outcomes) remains the same. If it needs to change I may
still be happy, but I'd want to see the changes first :)
-Rob