zendframework / zend-mime

Mime component from Zend Framework
BSD 3-Clause "New" or "Revised" License
62 stars 37 forks source link

MimePart is inefficient when handling in-memory data #16

Open GeeH opened 8 years ago

GeeH commented 8 years ago

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Original Issue: https://api.github.com/repos/zendframework/zendframework/issues/7471 User: @ddxor Created On: 2015-04-30T07:55:22Z Updated At: 2015-11-06T21:30:58Z Body MimePart requires that I pass it a type of resource as part of the object construct.

In my scenario I have just generated a PDF which I want to attach to an e-mail. Using MimePart I have to first write that PDF to disk, get a resource for it, pass that to MimePart which will then read it back from disk again.

This is wasteful IO. I should be able to pass MimePart a string and encoding type directly.


Comment

User: @Ocramius Created On: 2015-04-30T07:58:52Z Updated At: 2015-04-30T07:58:52Z Body You can create in-memory resources... On Apr 30, 2015 08:55, "James Anslow" notifications@github.com wrote:

MimePart requires that I pass it a type of resource as part of the object construct.

In my scenario I have just generated a PDF which I want to attach to an e-mail. Using MimePart I have to first write that PDF to disk, get a resource for it, pass that to MimePart which will then read it back from disk again.

This is wasteful IO. I should be able to pass MimePart a string and encoding type directly.

— Reply to this email directly or view it on GitHub https://github.com/zendframework/zf2/issues/7471.


Comment

User: @ddxor Created On: 2015-04-30T08:52:14Z Updated At: 2015-04-30T08:52:14Z Body MimePart already does what I want it to internally, just not as an option during construct. Even if I construct an in-memory resource I am still having to modify memory and waste resources doing so.


weierophinney commented 4 years ago

This repository has been closed and moved to laminas/laminas-mime; a new issue has been opened at https://github.com/laminas/laminas-mime/issues/6.