On 14/03/2011 11:14, Donal K. Fellows wrote:
On 11/03/2011 23:29, Guzman Llambias - INCO wrote:Donal Fellows wrote:Of more relevance is knowing what sort of message should be sent at that point. What porttype should we expect the remote service to implement? What security (if any)? Implementing something is possible, even easy, but we've got to get the details right.We're planning to use a ws-notification or ws-eventing endpointWith or without authentication? I ask because without is enormously easier because it means we can use simple tooling. Since the messages aren't intended to be long or hold secured information, it's quite possible to just use a UUID in the endpoint URL to keep things "safe enough". (Also, I don't think there's any plan at all to send out notifications "reliably"; authentication of the messaging would be much simpler than that!)
Also, they're both heavyweight protocols with a whole infrastructure for subscription, etc. This means that there's a whole lot of stuff to do to support them even minimally (i.e., just the MUSTs from the specs) that isn't there right now. Time to support... longer than I might otherwise hope. (Sending a notify message is easy enough, but all the infrastructure for managing subscriptions is rather complex.)
Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
_______________________________________________ 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/
