Community
Participate
Working Groups
Created attachment 92923 [details] Patch to generilize handling of lastModified timestamp The URLConnectionRetrieveFileTransfer and HttpClientRetrieveFileTransfer both obtain the 'lastModifiedTime' from the header fields for subsequent use when doing interrupted file transfer. This timestamp can be very useful when creating a local cache and it is not uncommon for remote protocols to support it. The attached patch will make the lastModified timestamp generally available in the IIncomingFileTransfer interface. It adds the needed functionality for the EFS provider as well (+ EFS support for getRemoteFileName()). I did not find a way to do this with SCP although I'm not a wiz in that area so perhaps that's possible too.
Created attachment 93000 [details] Patch with both lastModified and with reparenting This patch contains both the generalization of the lastModified timestamp and the reparenting of the IIncomingFileTransferReceiveStartEvent (as per discussion on ecf-dev list).
Will apply this patch and commit tomorrow am pacific time.
Applied patch, tested, updated IP log and committed to HEAD. Thanks again, Thomas. Bug #223019
(In reply to comment #3) > Applied patch, tested, updated IP log and committed to HEAD. Thanks again, > Thomas. > > Bug #223019 > Meant to put Bug #223019 next.
We are missing @since tags. I also think we should tag things as @since 2.0 (or @since 2.0.0) and not @since 2.0.0 milestone 6.
(In reply to comment #5) > We are missing @since tags. I also think we should tag things as @since 2.0 (or > @since 2.0.0) and not @since 2.0.0 milestone 6. > Added @since for new method, and changed tags to @since 2.0. Feel free to make such fixes directly where you observe them in the ECF codebase.
closing and contributed keyword