fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
fu ([personal profile] fu) wrote2011-01-11 12:54 am

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)

And I've implemented a new interface:

GET: service document / used to discover the APP URLs we provide

GET : lists the entries
POST: makes a new entry

GET: lists the journal's tags

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? :-)

[personal profile] faithofone 2011-01-27 03:33 am (UTC)(link)
Please forgive me if this comment makes no sense, I'm completely uneducated about how the whole atom thing works.

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.

[personal profile] faithofone 2011-01-30 06:37 pm (UTC)(link)
No need to be sorry about taking a few days, we all do that occasionally. Thank you for taking the time to reply. I appreciate your work to ensure that I can still spam my friends with tweets.