Hi Sylvain,

On 9/2/11 10:40 , "Sylvain Reynaud" <Sylvain.Reynaud@in2p3.fr> wrote:

Andre, I think you're right about the reason for the create() method ;

it can indeed return a Task object that will contain the created object.

I don't really understand that. So how does that differ from the LSU

functionality?

Mark, FYI you can configure JSAGA's "local://" adaptor to be mapped to

URL scheme "fork://"... but anyway, there are many other differences

between URL of various SAGA implementations (independently of the

implemented binding). The other main difference between SAGA

implementations is between the security contexts.

How come? Was there too much room for interpretation in the spec?

So if you want to develop an application that uses several SAGA

implementations, creating URLs and security contexts will require

implementation-specific code anyway.

I don't consider that a feature obviously.

It kind of defeats the purpose of having a standard API.

Cheers,

Mark

--

saga-rg mailing list

saga-rg@ogf.org

http://www.ogf.org/mailman/listinfo/saga-rg