hi dave,
yes, i forgot to specify the member / group actions. i took another
crack at it based on your suggestion. i wasn't sure of the preferred
terminology. i called the endpoint "members" and went from there:
http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_AAPP#section-Proposal_AAPP-MemberVerbs
another approach, which is what i was initially thinking, would be to
have weblog members be defined as part of the weblog entry (<weblog>),
and affected through the /aapp/weblogs endpoint by modifying the XML
content.
on the handling of the weblog user (aka creator, aka owner), it sounds
like we should simply not expose that and let permissions be handled
through the members endpoint. if i understand you correctly, the
creating user has no special significance after the weblog has been created.
thanks.
David M Johnson wrote:
On Jan 11, 2006, at 7:27 PM, Jeff Blattman wrote:
feedback appreciated.
http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_AAPP
Thanks for writing this up Jeff, we need this!
I know you're trying to simplify this, and that's good, but it seems
like you are missing an important piece.
A Roller weblog has a user, but that user is simply the user that
created the weblog and is NOT necessarily the "owner" of the weblog.
In fact, now that we have multiple users per blog, a blog can have
multiple admin users. So you can't set the owner of a weblog by
passing in just one username, unless you want to limit the protocol to
ONLY creating weblogs and allow no other operations on weblogs.
You have this:
GET all users
POST a new user
PUT user
DELETE user
And this:
GET all weblogs
POST a new weblog
PUT weblog
DELETE weblog
But is seems you also need this:
GET all users in weblog X
POST a new user in weblog X
PUT user (to change user's permission in weblog X)
DELETE user from weblog X
- Dave
