[Tickets #6957] Re: Problem with appledouble Viewer

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6957
------------------------------------------------------------------------------
  Ticket             | 6957
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Problem with appledouble Viewer
  Queue              | IMP
  Version            | 4.2
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2008-07-03 01:38) wrote:

> 1.- When I open the message my horde session is closed, I use
> memcache for session container. I have follow the code and I see the
> 'appledouble' Viewer has a 'new MIME_Contents()' and a posterior
> '$mc->buildMessage()' which cause that each part(>2Mb) is cached. OK,
> this is the cause of my closed session because in memcache the size
> limit per session is 1Mb, Is this right?

Wrong.  Sounds like you did not enable 'large_items' support in  
horde/config/conf.xml.  You can also change this value in the memcache  
source.

> This is correct?? And by other hand, Is right to store such large
> attachments in cache? It is better than to get directly the
> attachments from the IMAP Server?

This is a known limitation with Horde's MIME implementation.  See:
http://wiki.horde.org/Project/HordeMime?referrer=Projects#toc3

The short answer is - this data does not exist on the IMAP server, it  
is an "embedded" MIME Part.  Since we don't have a way to access the  
part without parsing the entire message again (and this may be  
difficult to do on a separate page), caching is the only way we can  
make these messages work.