Changes between Initial Version and Version 1 of Ticket #1373, comment 1


Ignore:
Timestamp:
2011-02-28T20:02:59Z (14 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1373, comment 1

    initial v1  
    1 Hmm, the encoding parameters of the existing file can be obtained from its URI, but how does {{{tahoe cp}}} know the current encoding parameters? It can't get them from {{{tahoe.cfg}}}, because its code directory may just have a {{{node.url}}} and no {{{tahoe.cfg}}}. Uploading a small file (just larger than the LIT threshold) and looking at the resulting URI would do it, but that's inefficient.
     1Hmm, the encoding parameters of the existing file can be obtained from its URI, but how does {{{tahoe cp}}} know the current encoding parameters? It can't get them from {{{tahoe.cfg}}}, because its node directory may just have a {{{node.url}}} and no {{{tahoe.cfg}}}. Uploading a small file (just larger than the LIT threshold) and looking at the resulting URI would do it, but that's inefficient.
    22
    33We may need a new web-API operation to get the encoding parameters.