On 09/04/2010 14:04, Alan Williams wrote:
Donal K. Fellows wrote:
I'd be tempted to say that something like this ought to be done fairly
soon. For one thing, it will solve quite a few problems in the Server,
not so much with the workflows themselves, but rather with how to handle
a number of policy issues that sit on the side, e.g., how to respond to
events. (Scripting allows some sophisticated behaviour.)

Yes I did think that having a scripted notification system would be "a
good thing".  Just as Taverna allows arbitrary (so long as they are
beanshell-speak) controls for service looping, it would be nice to do
that elsewhere.  I think that much of the code for a scripting service
could be used for scripting elsewhere; just as the beanshell service
code is re-used for looping control.

What I'd like is for there to be some sort of way for users to set up
code that can listen out for "interesting" events and do something with
them when they happen. Examples of doing something would include sending
the user an SMS, Twittering about it, or even submitting a paper to a
major journal with the results. OK, the last one is unrealistic. :-)

I don't want these to be part of the workflow itself as I think they'll
not have the same pattern of reusability. (I might use the same twitter
output for all of my workflows, but I don't want people I share them
with to twitter as me...)

OTOH, I don't think it's a good way to handle REST because it assumes
that all the knowledge about how to make a connection to a service can
be encapsulated in the workflow. Having a separate connector makes it
much easier to integrate with policy frameworks (e.g., on how to
discover service instances and authenticate to them).

That's an interesting idea.  I guess that will be part of your server
proposal?

Yes. I'm trying to keep the formation of connections to services as
something that is under control of some kind of policy system so that
there's a central point to apply things like security and rules for how
to find equivalent backup services. If this stuff starts getting spread
across lots of scripts then it will just be a horrible mess (such as
already exists with credentials and the R plugin).

Donal.

<<attachment: donal_k_fellows.vcf>>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
taverna-hackers mailing list
[email protected]
Web site: http://www.taverna.org.uk
Mailing lists: http://www.taverna.org.uk/about/contact-us/
Developers Guide: http://www.taverna.org.uk/developers/

Reply via email to