XML-RPC interface #48

Closed
opened 2007-05-21 19:19:26 +00:00 by zooko · 6 comments
zooko commented 2007-05-21 19:19:26 +00:00
Owner

Peter said he wanted an XML-RPC interface. Me, too! I nominate Brian to make one. ;-)

I've added a line to source:roadmap.txt about this. If you disagree or have other comments, Brian, please feel free to post to this ticket and to roadmap.txt.

Peter said he wanted an XML-RPC interface. Me, too! I nominate Brian to make one. ;-) I've added a line to source:roadmap.txt about this. If you disagree or have other comments, Brian, please feel free to post to this ticket and to roadmap.txt.
tahoe-lafs added the
code
major
enhancement
labels 2007-05-21 19:19:26 +00:00
zooko commented 2007-05-30 16:42:11 +00:00
Author
Owner

I'm raising the priority of this because I want it a lot and because #53 -- command-line interface -- could use this to connect to the daemon. See #60 about the question of what it means -- if anything -- to raise the priority of a ticket.

I'm raising the priority of this because I want it a lot and because #53 -- command-line interface -- could use this to connect to the daemon. See #60 about the question of what it means -- if anything -- to raise the priority of a ticket.
zooko commented 2007-06-28 15:57:08 +00:00
Author
Owner

This is assigned to me, and it is of high urgency.

This is assigned to me, and it is of high urgency.
tahoe-lafs added
blocker
and removed
major
labels 2007-06-28 15:57:08 +00:00
zooko commented 2007-07-01 03:45:25 +00:00
Author
Owner

Maybe I should have another look at WebDAV...

And we should definitely look at xuil (Brian is into this, too).

And the result might be more or less RESTful...

Maybe I should have another look at WebDAV... And we should definitely look at xuil (Brian is into this, too). And the result might be more or less RESTful...
warner commented 2007-07-11 22:27:19 +00:00
Author
Owner

since we have a working RESTful interface now, and since we're starting to write a CLI around it, I'm lowering the priority of this one.

since we have a working RESTful interface now, and since we're starting to write a CLI around it, I'm lowering the priority of this one.
tahoe-lafs added
major
and removed
blocker
labels 2007-07-11 22:27:19 +00:00
tahoe-lafs added
code-frontend-web
and removed
code
labels 2007-08-14 18:53:37 +00:00
tahoe-lafs added this to the undecided milestone 2007-10-10 23:16:40 +00:00
zooko commented 2007-10-19 23:10:51 +00:00
Author
Owner

I'm happy with [the RESTful interface]source:docs/webapi.txt, and so far our customers -- Dmitry and MikeB -- seem happy with it, and our CLI customer -- Zandr -- seems okay with the CLI, so I'm losing interest in writing another interface.

I'll regain interest if I detect another customer who would prefer XML-RPC over [the RESTful interface]source:docs/webapi.txt.

I'm happy with [the RESTful interface]source:docs/webapi.txt, and so far our customers -- Dmitry and MikeB -- seem happy with it, and our CLI customer -- Zandr -- seems okay with the CLI, so I'm losing interest in writing another interface. I'll regain interest if I detect another customer who would prefer XML-RPC over [the RESTful interface]source:docs/webapi.txt.
tahoe-lafs added
trivial
and removed
major
labels 2007-10-19 23:10:51 +00:00
tahoe-lafs modified the milestone from eventually to undecided 2008-06-01 20:57:17 +00:00
zooko commented 2008-06-10 02:55:02 +00:00
Author
Owner

Closing this as wontfix -- the RESTful interface is sufficient for now. This ticket will be reopened if we decide we want an XML-RPC interface.

(By the way, I recently heard that Amazon, which launched with both XML-RPC and REST, has 85% REST usage.)

Closing this as wontfix -- the RESTful interface is sufficient for now. This ticket will be reopened if we decide we want an XML-RPC interface. (By the way, I recently heard that Amazon, which launched with both XML-RPC and REST, has 85% REST usage.)
tahoe-lafs added the
wontfix
label 2008-06-10 02:55:02 +00:00
zooko closed this issue 2008-06-10 02:55:02 +00:00
Sign in to join this conversation.
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#48
No description provided.