Applications Messaging Standard

[Pierre Fernique]

Mark Taylor wrote:
> A standard API suggests language dependence, or at least an extension of 
> the standard for each newly endorsed language - to be avoided if at all 
> possible in my view.
> 
>>                                                    We might also
>> consider whether a simple, general naming service would be worth
>> defining for this sort of thing (XPA, being based on the X server,
>> which is unique for a user session, has this by the way; it supports
>> user sessions, distributed execution, and authentication - of course
>> it is also obsolete technology, and a bit platform specific).
> 
> 
> If there was such a pre-existing service which we could rely on finding
> in a usable state on the platforms which we needed to service, that 
> would be great.  Since there isn't, we'd need to specify one (or mandate 
> use of an existing one) and ensure that everybody who wanted to run 
> messaging-aware applications was running it. And then figure out the 
> protocol via which each participating application works out how to 
> communicate with it.  Back to square one.
> 
> In conclusion, I agree that storing bootstrap information in a ~/.ivoamsg
> file is a bit clunky and inelegant, and a bit fiddly from an application 
> author's point of view.  However it has the great advantage that it 
> requires no supporting system infrastructure other than a writable
> filesystem with per-user namespacing, and thankfully this exists on all
> the platforms that we want to support.  

Hi all,

I totally agree the Mark's point of view...

Regards
Pierre