![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Service Document?
Coming back with another question re: service documents, which was brought up in the comments to my earlier entry.
Is it better to consider the service document on a per-journal, or on a per-account basis? The service document is a URL you enter for your client to discover which URLs to use to post to a journal or a community.
I have seen two separate sets of suggestions, one that says to put the service document in:
http://www.dreamwidth.org/interface/atom
which lists your journal as well as any communities you have posting access to.
The other train of thought says to to put the service document in:
http://username.dreamwidth.org/interface/atom
And list only the collections (entries and eventually media such as images) that you can manipulate with that particular journal.
In both cases, entry posting will under journal space, such as http://username.dreamwidth.org/interface/atom/entries/1, etc.
I'm going back and forth on this one. I currently have the latter implemented, but am beginning to talk myself into the former. Before I tweak my code, though, I'm interested in hearing any more informed opinions on which option is the more standard.
On that note, the atom interface code is up on my public dev server, which is open for testing for anyone interested in trying it out with any clients you use. And if someone can point me to your favored client or service which uses APP, I'd like to try testing that on my own.
Is it better to consider the service document on a per-journal, or on a per-account basis? The service document is a URL you enter for your client to discover which URLs to use to post to a journal or a community.
I have seen two separate sets of suggestions, one that says to put the service document in:
http://www.dreamwidth.org/interface/atom
which lists your journal as well as any communities you have posting access to.
The other train of thought says to to put the service document in:
http://username.dreamwidth.org/interface/atom
And list only the collections (entries and eventually media such as images) that you can manipulate with that particular journal.
In both cases, entry posting will under journal space, such as http://username.dreamwidth.org/interface/atom/entries/1, etc.
I'm going back and forth on this one. I currently have the latter implemented, but am beginning to talk myself into the former. Before I tweak my code, though, I'm interested in hearing any more informed opinions on which option is the more standard.
On that note, the atom interface code is up on my public dev server, which is open for testing for anyone interested in trying it out with any clients you use. And if someone can point me to your favored client or service which uses APP, I'd like to try testing that on my own.
no subject
no subject
Given that we're heading towards a "one person, one account, multiple journals" method in the long run, the first option is probably best, IMO.
no subject
There is a reasonable case for supporting both, but it's not necessary and a maintenance hassle.
no subject