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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/11/12 20:09:14 UTC

[jira] Resolved: (JAMES-1128) Move messages from one queue to an other should try to not copy the message

     [ https://issues.apache.org/jira/browse/JAMES-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved JAMES-1128.
----------------------------------

    Resolution: Fixed
      Assignee: Norman Maurer

done.. no more copy needed when using BlobMessage :)

> Move messages from one queue to an other should try to not copy the message
> ---------------------------------------------------------------------------
>
>                 Key: JAMES-1128
>                 URL: https://issues.apache.org/jira/browse/JAMES-1128
>             Project: JAMES Server
>          Issue Type: Improvement
>    Affects Versions: 3.0-M1
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0-M3
>
>
> At the moment we use the FileSystemStrategy to store the message content to the filesystem. For this we use one directory per queue. So if we process a message in the spool and the move it to the outgoing queue (by RemoteDelivery) we need to copy the payload. Thats waste of I/O as as long as the message content was not changed we could just point to the "old" payload. So I think we should not use one different folder per queue. We should just use one folder for all queues.

-- 
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org