+1.
thanks.
David M Johnson wrote:
Anybody opposed to this small re-org / refactoring?
It's late in the release cycle, but this is a change that is safe and
has no impact on existing Roller features. The change will make my
life easier because I won't have to maintain a separate custom
directory for Atom protocol and Admin protocol work.
Here's what I'd like to do today:
1) Move Atom protocol implementation under package
org.roller.webservices.atomprotocol. Add a boolean startup property
(in roller.properties) to enable/disable it, default value is false.
2) Move Roller admin protocol implementation under package
org.roller.webservices.adminprotocol. Add a boolean startup property
(in roller.properties) to enable/disable, default value is false.
In case your wondering, here's some background:
* Atom protocol is a new IETF web services protocol for web
publishing, it does the same things as MetaWeblog API and more. The
spec is still under development and will be final this summer (I
hope). The Roller implementation supports the latest draft of the
spec (draft 8):
http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-08.html
* Admin protocol is a new REST based web services protocol for
managing Roller users and blogs created by Jeff Blattman of Sun for
Roller-Portal integration. It is based on Atom protocol and may
someday be replaced by an IETF standard, but since admin features have
been dropped from the current IETF Atom effort that may not happen for
a long time, Here's Jeff's original proposal:
http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_AAPP
- Dave
