Supporting Atom Publishing Protocol
I've been working on updating our implementation of the Atom Publishing Protocol for Bug 852, and I have a patch up there now.
Have several longish comments, but the short version is that our implementation was old to the point where I don't think any clients could use it, so I have felt free to break the old URLs while updating our implementation.
That is, I've removed support for:
http://www.dreamwidth.org/interface/atomapi/username/* (completely broken;
username had no effect on which journal the interface would use)
http://www.dreamwidth.org/interface/atom/feed
http://www.dreamwidth.org/interface/atom/post
http://www.dreamwidth.org/interface/atom/...
And I've implemented a new interface:
http://www.dreamwidth.org/interface/atom
GET: service document / used to discover the APP URLs we provide
http://www.dreamwidth.org/interface/entries
GET : lists the entries
POST: makes a new entry
http://www.dreamwidth.org/interface/entries/tags
GET: lists the journal's tags
http://www.dreamwidth.org/interface/entries/123
GET: retrieves entry 123
PUT: edits entry 123
DELETE: deletes entry 123
Does anyone have any concrete reasons I shouldn't push forward with this?
Also, any suggestions for how / whether to support posting to communities? What URL should we use? :-)
Have several longish comments, but the short version is that our implementation was old to the point where I don't think any clients could use it, so I have felt free to break the old URLs while updating our implementation.
That is, I've removed support for:
http://www.dreamwidth.org/interface/atomapi/username/* (completely broken;
username had no effect on which journal the interface would use)
http://www.dreamwidth.org/interface/atom/feed
http://www.dreamwidth.org/interface/atom/post
http://www.dreamwidth.org/interface/atom/...
And I've implemented a new interface:
http://www.dreamwidth.org/interface/atom
GET: service document / used to discover the APP URLs we provide
http://www.dreamwidth.org/interface/entries
GET : lists the entries
POST: makes a new entry
http://www.dreamwidth.org/interface/entries/tags
GET: lists the journal's tags
http://www.dreamwidth.org/interface/entries/123
GET: retrieves entry 123
PUT: edits entry 123
DELETE: deletes entry 123
Does anyone have any concrete reasons I shouldn't push forward with this?
Also, any suggestions for how / whether to support posting to communities? What URL should we use? :-)
no subject
Right now, I'm using the atom api with Loudtwitter to post my twitter digests. The URL that I'm using is http://www.dreamwidth.org/interface/atom/post
If you're removing that URL, it'll break my twitter syndication, and it would be sad making.
no subject
I will test this against LoudTwitter, and do what it takes to prevent this setup from breaking!
no subject