[tahoe-lafs-trac-stream] [Tahoe-LAFS] #567: add version info to t=JSON output data

Tahoe-LAFS trac at tahoe-lafs.org
Tue Nov 29 11:40:16 UTC 2016


#567: add version info to t=JSON output data
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  rvs
         Type:           |     Status:  assigned
  enhancement            |
     Priority:  major    |  Milestone:  soon
    Component:  code-    |    Version:  n/a
  frontend-web           |   Keywords:  version json docs easy forward-
   Resolution:           |  compatibility
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by rvs):

 * owner:  nobody => rvs
 * status:  new => assigned
 * version:  1.2.0 => n/a


Old description:

> It will probably make life easier in the future if we add a version
> number to the JSON output from operations like {{{deep-stats}}}, {{{deep-
> manifest}}}, and {{{deep-check}}}.
>
> A related piece would be to tell developers that they should tolerate the
> presence or absence of each field.
>
> On the other hand, the only customers of the t=JSON are:[[br]]
>  1) The Tahoe CLI[[br]]
>  2) Tools written to use the webapi functions[[BR]]
>
> I'm ok with requiring that you use e.g. a 1.3.0 CLI with a 1.3.x backend
> instead of a 1.4.x backend, and developers have to play catchup all the
> time anyways. So I'm not sure how much energy I want to put into this.

New description:

 It will probably make life easier in the future if we add a version number
 to the JSON output from operations like {{{deep-stats}}}, {{{deep-
 manifest}}}, and {{{deep-check}}}.
 A related piece would be to tell developers that they should tolerate the
 presence or absence of each field.
 On the other hand, the only customers of the t=JSON are:[[br]]
  1) The Tahoe CLI[[br]]
  2) Tools written to use the webapi functions[[BR]]
 I'm ok with requiring that you use e.g. a 1.3.0 CLI with a 1.3.x backend
 instead of a 1.4.x backend, and developers have to play catchup all the
 time anyways. So I'm not sure how much energy I want to put into this.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/567#comment:21>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list