You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by ji...@apache.org on 2004/05/21 08:06:01 UTC

[jira] Commented: (JAMES-288) memory efficient retrieval

The following comment has been added to this issue:

     Author: Ralf Hauser
    Created: Thu, 20 May 2004 11:04 PM
       Body:
For this delayed retrieval to work nicely, I had to add to MailImpl
    private long sizeForDelayed = -1;

and adapted the getMessageSize() with
    	if (state.equals(MailRepository.DELAYED)){
    		return sizeForDelayed;
    	}

since in the stat(), I only do set the mipl.setName() and mipl.setSizeForDelayed(size);

This way, later doLIST can be executed arbitrary many times even if single messages are nullified as per http://nagoya.apache.org/jira/browse/JAMES-248
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JAMES-288?page=comments#action_35661

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-288

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-288
    Summary: memory efficient retrieval
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: James
 Components: 
             POP3Server
   Versions:
             2.1.3

   Assignee: 
   Reporter: Ralf Hauser

    Created: Tue, 18 May 2004 9:38 AM
    Updated: Thu, 20 May 2004 11:04 PM
Environment: redhat 9

Description:
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?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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