On 09/04/2010 11:50, Alan Williams wrote:
> Much more could be gained by providing a capability for T2 to run > script languages such as Ruby which has several well developed and > battle tested frameworks, each aimed at making it easy to consuming > HTTP (and other protocol) services, RESTful or not.At the moment Taverna is in Java 1.5. If we move to 1.6 then we can use the Java Scripting API, for which there is a Ruby Engine. At the moment there is a beanshell script service in Taverna; that could be generalized to a script service.
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.) 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). Scripting this all makes it much more awkward. Where I think scripting would really shine is in the definition of shims. Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------ Download Intel® 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/
