tahoe-lafs/trac-2024-07-25

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

New issue

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

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

and removed

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 labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1541

No description provided.