[saga-rg] Jobs and SandBoxing

[Christopher Smith]

On 19/8/05 10:15, "Andre Merzky" <andre at merzky.net> wrote:

>> The idea is that two SAGA implementations (running
>> concurrently) would have globally unique job id spaces.
> 
> I can think of two ways to create such ideas.
> 
>   A: create a unique string (MD5 or so) and make an external
>      entity responsible for maintaining the mapping between
>      that ID and the backend instance and native job id.
>      One could also allow a non random string (e.g. a user
>      specified name), but the naming collision problem is
>      then moved into user space.
>   
>   B: combine backen-url and native jobID in a well defined
>      (i.e. parsable) way.  Possibly allow to add another
>      part as user specific.
> 
>      <free string>-<backend url>-<nativeID>
>      <MyJob>-<gram://www.test.net:1234/>-<SAD12412SDF>
> 
> B seems simplier, and does not introduce an external
> dependency.  The free string would allo the user to
> recognice the jobs - nice for browsing.  Could default to
> the executable name or so.
> 
I like this mechanism as well, although I'm ok with just
<backend url>-<nativeID> without the user specified identifier (there are
still job names after all).

> I am pretty sure it braks for some cases. E.g. the backend
> may have a moving URL, or may reuse ID's (as Unix does with
> pid's).  However, as long as it is not mandatory, it might
> just help...
> 
You're right, but it would be useful for many cases.

-- Chris