Take a look at the histories controller (histories.py) for an example + documentation on how Galaxy realizes a RESTful interface. In short, you'll want to implement different methods for create, read, update, and delete. Kwds are miscellaneous parameters included in a request that are not explicitly specified in a method signature.
Good luck, J. On Sep 13, 2013, at 7:52 PM, Ted Goldstein, Ph.D. wrote: > I've been knocking my head over this all afternoon and I was hoping to buy a > vowel, use a lifeline, whatever. > > I'm trying to use the Ember JS framework (which is very nice) for some > extensions. It relies heavily on a REST model using the same method with all > of the HTTP forms including > > Action HTTP Verb URL > Find GET /people/123 > Find All GET /people > Update PUT /people/123 (with the HTTP payload packed with the > JSON content) > Create POST /people > Delete DELETE /people/123 > > How can I make an API function that responds to all five forms and what > should be in buildapp.py? > > All of the code in Galaxy currently uses the kwd (keyword) parameter. But > there are no keywords here. > > Confused, > Ted > > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > http://lists.bx.psu.edu/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/