On 06/22/2017 12:20 AM, Daniel Stenberg wrote:
On Wed, 21 Jun 2017, Patrick Monnerat via curl-library wrote:
As we may now be ready to add new entry points for form handling, I
wonder if the new form API should not be extended to some more
generic API, capable of building a data stream from different
components for any Mime oriented protocol, reducing the need of some
external Mime library for calling applications. After all, forms are
a subset of Mime. This could probably be achieved without a too large
"code bloat".
I suppose you're then thinking of uses cases like actually providing a
mail body for sending with SMTP etc?
Yes, SMTP is the main target of my idea. But this could also be used for
storing in IMAP.
The form API would need to become a much more generic MIME API for it
to work good for that. But sure, if someone has use cases in mind and
want to suggest how the current form API redesign proposal can be made
into a more generic MIME one, then I could be interested.
Having a mean to get a handle for each subpart could be an elegant way
of doing that. I'll investigate for some proposal.
I just don't want it to be made into a super big and complicated
project because of that...
... that's why I wrote about "code bloat".
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
