Re: [Exist-development] My vision about admin RESTful URLs

[Dan M. <dan...@gm...>]

eXcellent feedback Tomas.

You have a nice holistic view of other areas of administration that I
had not considered for RESTful interfaces.

A few small suggestions.

To be consistent with the /admin/{object}/{action} format, perhaps we
could officially use "server" as a named object.

So the following might be some actions on the database server:

/admin/server/shutdown
/admin/server/restart
/admin/state/status
/admin/state/statistics

etc.

This might be a little more precise then the label "do".

I would also like to keep all the operations on collections in a
single areas so that we can enable/disable collection operation
buttons.  So if you specify:

/admin/collection

The REST interface would return a list of all possible operations on a
collection:

Create New Index, Edit Index, Estimate Index Creation Time, Index
(Reindex) Collection, Update Index, Change Owner, Change Permissions,
Create New Trigger, Edit Trigger, Add Version, Move, Rename,
Collection Size, Synchronize, Edit Access Policy, Upload Files,
Collection Details, Delete Collection, Copy, Backup Collection,
Restore Collection, Create a New Subcollection

Perhaps I should refactor the collection admin database to include a
single object type code list:

The list of possible admin objects might include:

configuration-file
collection
group
index
log-file
policy
resource
server
trigger
user

etc.

I also would like to suggest we talk to Loren about how we might
create a RESTful interface to an existing logfile analyzer like
"Apache Chainsaw".

See http://logging.apache.org/chainsaw

Loren is an expert on logfile viewing and has already spent a great
deal of time thinking about integrating Apache Chainsaw with eXist.

- Dan