Add ?t=xml parameter for getting file statistics #1541

Open
opened 2011-09-25 00:37:07 +00:00 by bibilthaysose · 1 comment
bibilthaysose commented 2011-09-25 00:37:07 +00:00
Owner

The best way to programmatically retrieve file statistics is currently with GET /uri/$PATH?t=json. However, xml has some advantages (such as xpath, xsl, xsv) over json.

The general consensus seems to be that converting generically between json and xml is problematic because of things like attributes, cdata and textual elements. However, I believe that these difficulties are only encountered when translating richly written xml (that makes use of the aforementioned artifacts) to json. It seems like going from json to xml should not carry such difficulties.

There is a library of xsl functions called fxsl which contains a function called f:json_document(). This would require the libxslt (and libxml2) module if it were to be used on the server side.

The best way to programmatically retrieve file statistics is currently with GET /uri/$PATH?t=json. However, xml has some advantages (such as xpath, xsl, xsv) over json. The general consensus seems to be that converting generically between json and xml is problematic because of things like attributes, cdata and textual elements. However, I believe that these difficulties are only encountered when translating richly written xml (that makes use of the aforementioned artifacts) to json. It seems like going from json to xml should not carry such difficulties. There is a library of xsl functions called fxsl which contains a function called f:json_document(). This would require the libxslt (and libxml2) module if it were to be used on the server side.
tahoe-lafs added the
unknown
major
enhancement
1.9.0a1
labels 2011-09-25 00:37:07 +00:00
tahoe-lafs added this to the eventually milestone 2011-09-25 00:37:07 +00:00
davidsarah commented 2012-03-29 19:30:00 +00:00
Author
Owner

I'm -1 on this ticket because I think it's unnecessary complexity.

I'm -1 on this ticket because I think it's unnecessary complexity.
tahoe-lafs added
code-frontend-web
normal
and removed
unknown
major
labels 2012-03-29 19:30:00 +00:00
tahoe-lafs modified the milestone from eventually to undecided 2012-03-29 19:30:00 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1541
No description provided.