Hi,
I'm afraid this problem may be unavoidable due to the way S3 object copying works. From your experience, it looks like S3 will not actually cancel a copy operation when you break the HTTP connection. This makes some sense, because the ongoing HTTP connection is only really used so S3 can inform clients of the progress of the copy operation.
Because the copying itself is done on the back-end, I guess S3 doesn't really care if the client breaks its connection.
You should confirm this behaviour by asking a question in the S3 forums, but if I'm right in thinking that the copy will proceed regardless of what the client does, then you cannot really cancel a copy once it has started.
If you need to really cancel the copy operations, you many need to perform them one at a time so that when the user cancels the overall copy process, any individual object copy steps that haven't yet started will never start. If that makes any sense?
Hope this helps,
James
---
http://www.jamesmurty.com
On Fri, Feb 13, 2009 at 9:02 PM, TejKiran
<tejkiransharma@...> wrote:
Hi,
When I do copy operation for any file and in between of COPYING process I
stopped that process.
Then it shows failed the process. it shows that copy has been failed but
when I check at that location, I found that all failed files also has been
copied there.
I am using copyObjects() of S3ServiceMulti. class for copy operation. And
also I am handling S3ServiceEventListener
So when I pause or stop any running thread its show stop/pause status and
copyObjects method also returning failed but it coping the objects.
If any body have suitable suggestion/ solution for it, please reply...
--
View this message in context: http://www.nabble.com/S3ServiceMulti%27s-copyObjects%28%29-not-getting-stopped...-tp21993452p21993452.html
Sent from the JetS3t Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
