james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <server-...@james.apache.org>
Subject [jira] Assigned: (JAMES-288) memory efficient retrieval
Date Mon, 06 Mar 2006 12:49:31 GMT
     [ http://issues.apache.org/jira/browse/JAMES-288?page=all ]

Stefano Bagnara reassigned JAMES-288:

    Assign To: Stefano Bagnara

> memory efficient retrieval
> --------------------------
>          Key: JAMES-288
>          URL: http://issues.apache.org/jira/browse/JAMES-288
>      Project: James
>         Type: Improvement
>   Components: POP3Server
>     Versions: 2.1.3
>  Environment: redhat 9
>     Reporter: Ralf Hauser
>     Assignee: Stefano Bagnara

> 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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message