Hi, On Jan 30, 2008 10:55 PM, Pat Cappelaere <[EMAIL PROTECTED]> wrote: > > I am trying to document a potential call to get the Engine Status > Like in: > > GET /wfcs/engine > > I would probably expect to get the engine status (running, paused...) and > a list of running/scheduled processes. Anything else?
Shouldn't the list of running/scheduled processes belong to GET /processes ? It's how it's currently implemented in Kisha. > So I can now find the jobs on the schedule, I can get the job_id and the job > object. I can get the schedule_info on that object. > > How do I get the wfid short of parsing the ascii string that could be in the > job_id (could also be a counter, I guess)? I am not seeing any convenience > functions. I can always write one :) IIRC, the process waiting to get scheduled has still no wfid, it'll get one at the moment it is launched. > The other thing is that I am not too pleased in the WfXML document is about > the halt/resume cmds to the engine. REST would suggest a PUT like: > PUT /wfcs/engine > <entry... > <cmd>halt|resume</cmd> > </entry> > > Wondering if it would be acceptable to deviate and use something like: > > GET /wfcs/engine?status=halt | pause | start | stop > > Or even > GET /wfcs/engine/halt > > WDYT? GET shouldn't modify anything. > Technically start and stop ought to be POST and DELETE too. start process, stop process... launch process is a POST, cancel process a DELETE, why not. start engine, a POST on /engines, stop engine, if it's a DELETE, it implies that the engine cannot get restarted... > And can we assume one engine resource only? In which context ? In your document, you seem to be assuming one [RESTful] host and potentially multiple engines. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
