[Email-SIG] FeedParser: Incremental Payload Reporting
Clark C. Evans
cce at clarkevans.com
Sat Jan 15 22:55:39 CET 2005
On Sat, Jan 15, 2005 at 03:58:58PM -0500, Barry Warsaw wrote:
| > couldn't the Message class be
| > extended to have an "write_payload()" method instead?
| Yep, and there have been some discussions about this, so check the
| archives. It's what I meant when I talked about 'external storage API'
| in the list of possible sprint topics.
Fantastic... I can hardly wait!
| > I'm also confused at push() in lines 96 to 110. How does this work
| > with a binary payload?
| It doesn't, but that's not a use case the FeedParser really needs to
| worry about. Email is always line-oriented text, and binary messages
| are encoded into stuff like base64 so we can cheat this way.
I'd like to use the FeedParser for use parsing multipart/form-data
from a HTTP POST, and in this case the most common file content is
binary and the encoding is... none. Could this be added to the
wish-list? It'd also allow cgi.py to be refactored nicely.
Clark C. Evans Prometheus Research, LLC.
o office: +1.203.777.2550
~/ , mobile: +1.203.444.0557
(( Prometheus Research: Transforming Data Into Knowledge
\/ - Research Exchange Database
/\ - Survey & Assessment Technologies
` \ - Software Tools for Researchers
More information about the Email-SIG