Re: [Exist-development] List of collection actions for administration tool

[Thomas W. <tho...@gm...>]

I would like to propose an "object-action" name convention. For example:
      collection-create
       collection-delete
      collection-copy
      collection-move
      index-create
      index-update

To me it is more natural to define the entity I  am going to work with
first, and then talk about the action.

Thomas

------

Thomas White

Mobile:+44 7711 922 966
Skype: thomaswhite
gTalk: thomas.0007
Linked-In:http://www.linkedin.com/in/thomaswhite0007
facebook: http://www.facebook.com/thomas.0007



2009/11/18 Adam Retter <ad...@ex...>

> > By creating RESTful interfaces for each action we can do UNIT testing on
> the
> > actions and also allow anyone to easily extend the interface to match
> their
> > requirements.
>
> You can also decide on the UI later, or create more than one possible
> UI that uses the same back end.
>
> I suggest that all back-end REST interfaces are constructed and tested
> in advance of any UI code!
> I would also suggest that the back-end should follow an MVC
> approach... well at least the M and C parts for the time being!
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>