On 7/24/07, Matt Zukowski <[EMAIL PROTECTED]> wrote: > > Pat, I'm intentionally trying to keep this dead simple. Our needs and > scope for this are limited and rather short-sighted, so I'm avoiding > trying to build a grandiose framework. All I need is something that > lets me expose an external API for creating workflows, feeding > additional data into a running workflow (e.g. the result of some human > approval request step), and fetching information about the status of a > given workflow (i.e. where it's currently at, what it's waiting for, > etc.)... I've picked REST because it's simple and easy to implement in > our client apps. > > I have a feeling that the end result will be somewhat loose and un- > enterprise-y. A 171-page API spec is definitely not something I was > intending on implementing (or even looking at, really). Despite this > though, I think that the end result will be a small, agile app filling > a pretty deep niche. We -- and I suspect many others -- just need > something that handles relatively simple business processes like > request approvals, document filing, etc. > > That said, I do want to make sure that I've got my head wrapped around > the key concepts here, so as not to come up with something that isn't > awkward (and the fact that I'm having a hard time getting a feel for > OpenWFEru's semantics makes me feel like I haven't yet quite gotten a > good feel for what this is all about.... the alternative being that > OpenWFEru is just awkward :).
Matt, if you feel you're losing time with OpenWFEru, please try another workflow engine or implement your own. No problem if it doesn't fit your mindset, the world of open source is one of choices. About a standard API, I see none as standard, and from far, they all look damn ugly and fat. With OpenWFEru I could get liberated from Java and its horde of standards. I really want OpenWFEru to stay something tiny (I'll have to get rid of some inherited fat... And well it's not that tiny). Like Matt, I want to have the simplest, smallest API possible, it's always possible to slap a damn ugly standard interface on top of it later (like I did for the old OpenWFEja REST interface (which of course is not standard)). 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 -~----------~----~----~----~------~----~------~--~---
