Hummm!. It could be argued that a web application is always a web service (to the user) so a consistent API is always important for the user experience as a whole across services. It would make everybody's life easier if we could stick to consistent patterns (hence ROA). I guess that it is just a matter of time... Pat.
> From: John Mettraux <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > Date: Sun, 16 Sep 2007 16:34:29 +0900 > To: <[email protected]> > Subject: [openwferu-dev] Re: Densha launch with parameters > > > On 9/16/07, Juan Pedro Paredes <[EMAIL PROTECTED]> wrote: >> >> >> >> On 15 sep, 04:32, Pat Cappelaere <[EMAIL PROTECTED]> wrote: >>> I think that in a real-like application, workflows will be stored in >>> databases along with some meta-data and fully versioned. They are not >>> really url's (although they can be addressed by their urls if needed. They >>> are resources after all ) >> >> A url can be something like >> db://table/process/v1 >> Do you know wat i mean? :). I's only overload the ruby handler. >> But do debug and devel purposes is more usable >> file://where >> >> I'm very interested to store all workflow data and metadata in >> activerecord (or some other scalable transactional store). >> AFAIK in densha, not all the process workflow stuff resides in >> database. >> There are some expool a journal files. >> >> I think this a good path, to make it as reliable and scalable as >> possible. > > Hi Juan Pedro, > > currently workflow run data is stored in the filesystem, because this > is cheaper and that it's not relational data, just data with one index > (the flow expression id). Only the engine consumes such data, there is > no point in making it available to other applications (other than > engines). > > I've been thinking about storing that in a RDBMS via AR, this will end > up in a table with 2 columns (fei and content). There is only thing > that scares me : the engine tends to access this rundata rather > frequently, fortunately it's easy to diminish the access frequency via > caching and slightly delayed storage, see > "ThreadedYamlFileExpressionStorage" in : > http://viewvc.rubyforge.mmmultiworks.com/cgi/viewvc.cgi/trunk/openwfe-ruby/lib > /openwfe/expool/yamlexpstorage.rb?root=openwferu&view=markup > > I will perhaps implement this workflow run data AR persistence if a > real need arise. > > Densha stores workitem via AR because they are what stands between the > engine and its end-users. Workflow rundata on the other end is only > accessed by the engine. > > > 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 -~----------~----~----~----~------~----~------~--~---
