[cvs] [Wiki] changed: Project/HordeMime

[Michael Slusarz]

slusarz  Wed, 19 Nov 2008 00:46:51 -0500

Modified page: http://wiki.horde.org/Project/HordeMime
New Revision:  1.14
Change log:  this is pretty much completed

@@ -5,10 +5,10 @@
  The MIME packages need to be rewritten in BC-breaking ways to add  
features and for Horde 4.0. All code that remains in the framework  
should be changed to have the prefix {{Horde_Mime}} (instead of just  
{{MIME}} - the case change is also intentional). The code should also  
be updated to use PHP 5 features.

  ++ Bugs

-[http://bugs.horde.org/ticket/1866 Bug #1866]
-[http://bugs.horde.org/ticket/3580 Bug #3580]
+[http://bugs.horde.org/ticket/1866 Bug #1866] **FIXED**
+[http://bugs.horde.org/ticket/3580 Bug #3580] **FIXED**

  ++ People

  Michael Slusarz has been the lead developer on the MIME package  
lately. He is actively working on portions of this project in  
association with creating the new Horde IMAP library. Jan Schneider  
has done work on it as well. Chuck Hagenbuch is not an expert in the  
current code but is interested in this project and knows the area in  
general.
@@ -25,22 +25,22 @@
        1. text/plain
        2. image/jpeg
  </code>

-Then, if we want to access the image/jpeg option, we do a  
getPart('2.2') call to the MIME_Contents:: object and it will be  
responsible for rebuilding the data (it sees that 2.2 doesn't exist on  
the IMAP server, but that id 2 containsembedded data, so it  
automatically downloads/parses as many parent parts as required to  
build down to the requested part).  This will eliminate the need for  
MIME specific caching - which was always kind of a hackish  
implementation by me I admit.
+Then, if we want to access the image/jpeg option, we do a  
getPart('2.2') call to the IMP_Contents:: object and it will be  
responsible for rebuilding the data (it sees that 2.2 doesn't exist on  
the IMAP server, but that id 2 contains embedded data, so it  
automatically downloads/parses as many parent parts as required to  
build down to the requested part).  This will eliminate the need for  
MIME specific caching - which was always kind of a hackish  
implementation by me I admit. **FIXED**

  +++ More notes

  Status of work that needs to be done for the various MIME components.

  ++++MIME_Part
-Should do a better job of natively handling 'message/rfc822' parts -  
i.e. having a specific 'rfc822BasePart()/setrfc822BasePart()' methods  
to return/set the ID of the message/rfc822 part that is the parent of  
the current part (rather than using  
setInformation()/getInformation()).  For IMP, we may want to override  
MIME_Part (esp. setContents()/getContents()) to obtain the information  
from the IMAP server - although haven't decided yet whether this  
should remain in IMP_Contents/MIME_Contents::, or even MIME_Viewer::.
+

  ++++MIME_Message
-No major changes.  Maybe try to clean up rebuild code a bit - but it  
works so don't mess with it too much.
+No major changes.  Maybe try to clean up rebuild code a bit - but it  
works so don't mess with it too much. Moved parsing of message from  
the old MIME_Structure into this.

  ++++MIME_Structure
-Will be removed.  Parsing functions will be moved to MIME_Message and  
MIME_Headers.
+Will be removed.  Parsing functions will be moved to MIME_Message and  
MIME_Headers. **REMOVED**

  ++++MIME_Headers
  Remove deprecated code.  Remove all c-client specific code.  Library  
will focus exclusively on parsing Headers and presenting an easy to  
use access to header fields (with associated MIME decoding).  All  
functions relating to UI display (such as altering headers in  
preparation for display) will be removed.