[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-email-sig
Subject:    Re: [Email-SIG] Proposed Enhanced MIME Handling API
From:       "R. David Murray" <rdmurray () bitdance ! com>
Date:       2013-09-24 1:40:41
Message-ID: 20130924014042.8BCE6250965 () webabinitio ! net
[Download RAW message or body]

On Mon, 23 Sep 2013 15:14:17 -0700, Forest <web11.forest@tibit.com> wrote:
> On Fri, 30 Aug 2013 23:35:28 -0400, R. David Murray wrote:
> >No response means nobody objects, right? :)
> 
> Hi, David.  You can count me among those who are interested but busy.  :)

:)

> I remember you mentioning in the past that data streaming was a development
> goal.  Is it a priority yet?  Even if not, would this be a good time to
> define a streaming interface for creating/reading/writing custom content
> objects, so that the standard library's internal code can eventually be
> rewritten to use it?  I'd hate to see everyone's shiny new content managers
> end up blocking progress on data streaming due to a design incompatibility.

I would say that that was the goal that is next on my list.  The problem
with it is that the current parser and generator do *not* support
streaming (despite the parser being named 'feedparser'...you can stream
data *in* to it, but you can't get the message parts to stream *out*
of it...the entire message is held in memory; although that said it will
be the easier of the two).

Something I wanted to do but ran out of time for was to add policy
hooks to implement external storage of bodies.  That is probably the
key piece needed for streaming, although by itself it doesn't solve the
generator problem.

Figuring out how to make all this work is not going to be trivial,
so I'm not sure there's any way to even get an API figured out before
3.4 beta.  If you've got suggestions, though, I'm all ears.

--David
_______________________________________________
Email-SIG mailing list
Email-SIG@python.org
Your options: https://mail.python.org/mailman/options/email-sig/python-email-sig%40progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]