Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <12849725.1187473410872.JavaMail.jira@brutus>
Date: Sat, 18 Aug 2007 14:43:30 -0700 (PDT)
From: "Oliver Zeigermann (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Resolved: (TRANSACTION-12) Use NIO for file copying/moving
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/TRANSACTION-12?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Zeigermann resolved TRANSACTION-12.
------------------------------------------

    Resolution: Fixed

Copying and moving not benefits from NIO.

> Use NIO for file copying/moving
> -------------------------------
>
>                 Key: TRANSACTION-12
>                 URL: https://issues.apache.org/jira/browse/TRANSACTION-12
>             Project: Commons Transaction
>          Issue Type: Wish
>    Affects Versions: 1.2
>            Reporter: Holger Hoffst=C3=A4tte
>             Fix For: 2.0
>
>         Attachments: moveByRenameAndNIO.txt
>
>
> The Mule project (http://mule.codehaus.org/) is considering adoption of c=
ommons-transaction for (among other things) file transactions. Unfortunatel=
y inspection of the code reveals that FileHelper copies files in the slowes=
t possible way (traditional Java I/O via Input/OutputStreams). Since some o=
f our users move lots and/or large files (hundreds of megabytes to gigabyte=
s) we implemented file moving by rename (atomic and obviously very fast whe=
n source and target are on the same filesystem) and NIO as backup strategy =
(a lot less CPU usage).
> Attached is a code snippet that outlines the procedure; it would be cool =
if c-tx could adopt a similar strategy for moving via rename-first and copy=
 via NIO. I do not know if and how this might conflict with c-tx's "transac=
tional" behaviour and recovery but then again it is just a suggestion. :-)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.