[
https://issues.apache.org/jira/browse/JAMES-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved JAMES-288.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: Trunk)
2.3.0
AFAIK we removed the full in memory load of messages on pop3 retr in 2.3.0 in
favor of streaming.
In the stat/list command there is a lot of space of optimization, but this is a
first step.
> memory efficient retrieval
> --------------------------
>
> Key: JAMES-288
> URL: https://issues.apache.org/jira/browse/JAMES-288
> Project: James
> Issue Type: Improvement
> Components: POP3Server
> Affects Versions: 2.1.3
> Environment: redhat 9
> Reporter: Ralf Hauser
> Assigned To: Stefano Bagnara
> Fix For: 2.3.0
>
>
> After analyzing what happens when I retrieve mail, I noticed that james at
> the end of doPASS does a stat() that brings all messages in their entirety
> (not just referenced by their key) into the JVM irrespective whether they are
> already read or not.
> later the MUA then will doRETR() selected messages.
> It appears to me that this may lead to problems if either messages are large
> or with many simultaneous user sessions.
> Why not wait with the retrieve (from file or JDBC) until the MUA's doRETR
> arrives?
> If the MUA first only gets a few hundred header characters and then comes
> back again, one might accomodate this by on-demand-insertion or rather
> upgrade in doRETR. This previously happened in stat() with
> userMailbox.addElement(mc);
> What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
