Re: [Openflow-dev] OpenFlow thoughts

[<jm...@so...>]

On Mon, 7 Jan 2002, Shane Hathaway wrote:

> I need to understand better what an application is.  Is its purpose to
> allow you to poke an URL when an activity happens?  If so, it might be
> better to create a general-purpose Zope URL Poker and allow the workflow
> to use any callable Zope object as a hook.

On the beginning, there were no automatic activities. All were called
througth the "ToDo List", and they were launched calling them via the
browser, so via an url. This url, PLUS the parameters is what the
application represents.

Now, you can switch very fast from the automatic to the manual mode. I
think this is one of the most important values which diferentiates
Openflow from a programming languaje like python, where all the steps are
automatic (programmed) by definition. Here, if you have a problem with a
step, you can put it in manual mode, DO IT (there is always a way of
doing it), WHILE you try to correct the problem. Or, for example, you can
realize an activity manually at the begining, but when you see that
everything works well ... switch to automatic mode, so you don't need to
explicitly aprove them.


Suppose that an application is defined through a Zope object, and not a
url: you loose this facility. Well, in fact, every Zope object has one or
more urls ...

Well, giving a Zope object instead of a url could have a benefit: using
the "Lock Folder" product, you can avoid that an object cannot be accessed
via its url. So it could be usefull in some cases.


More thoughts ???  ;.-))



--=20

      __o
    _ \<_
   (_)/(_)

Saludos de Juli=E1n
EA4ACL
-.-