On 7/24/07, Matt Zukowski <[EMAIL PROTECTED]> wrote: > > 8< > > To me, the fact > ath I don't need a workflow id suggests that I'm not really updating a > workflow resource -- I'm updating something else... a participant, a > workitem... I don't know. So maybe this is where trying to use a > "Workflow" as my REST resources breaks down? Maybe my REST operations > should be centered around a difference concept than the "Workflow"? > Can you suggest something? On the other hand, maybe using a "Workflow" > as the resource isn't wrong... only that a workflow system doesn't > quite lend itself to CRUD operations, and it's okay to bend the > meaning of the REST verbs here....
As you've said trying to stick CRUD on the concept of "workflow" is hard. Have you reflected about the concept of worklist ? What are your use cases ? Do you want workitems to wait for manipulations by other systems (users ?) ? You're not tied to have 1 unique concept to slap CRUD on top of. Other concept you can use : "worklist" / "workitem" / "participant" / ... 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 -~----------~----~----~----~------~----~------~--~---
