[Pipet Users] Update

[Nicolas Chauvat]

> Currently Piper doesn't support inter instance communications, just
> because we never had the time for it. (Sounds like a deja-vu) So we
> still have the luxury of a free choose now.
> 
> By inter instance communication I'm trying to say this:
> 
> Piper                                    Piper
> running on  --?KQML?--  running on
> machine A                           machine B
> 
> It's the BL that will handle this communications, so we COULD just
> design what we need and implement this. But I think a mayor feature
> would be if these communications were based on a standard so it can
> comm. with other legacy systems to. Kqml seems to be designed for this
> purpose. Why do you think it isn't?

I'm not sure I have an opinion yet. Mainly because I'm not clear what kind
of messages you want these piper instances to exchange. I'm sorry if the 
best answer to my question is "tfm says that", I never managed to get a
clear understanding of the roles of the various piper layers when reading
the documentation. And I never got time to read the code...

Could you explain again what those messages would be like: what is their
purpose, what kind of embedded information/data do they transport, etc.

As far as KQML as an intercommunication language, I've had bad experiences
with it, mainly because it's not really a standard, so you end up with a
lot of KQML dialects. That can be worse than having "piper's own
communication language" and providing KQML translators for specific
applications.

-- 
Nicolas Chauvat

http://www.logilab.com - "Mais où est donc Ornicar ?" - LOGILAB, Paris (France)