[Fusioninventory-devel] Questions about extensions and REST/JSON proposal

[Alejandro]

Hi Gonéri

The AMQP connector I tested is
https://github.com/joodie/poe-component-client-amqp (Also in CPAN, but
corrected version is here), is in pure perl.
The problem: Use POE (in reality isn't a problem because POE is all pure
perl).

There are other library I want to use: Crypt::OpenSSL::RSA, but need openssl
(libssl). I want to use it to crypt messages so only the agent and
dispatcher can read them.
There are any problem with this library?

If you think that AMQP could be too complex, I can do a erlang extension in
rabbitmq server to provide a JSON/REST bridge.

Thanks.



El 7 de abril de 2011 13:01, Benoit Mortier
<benoit.mortier at opensides.be>escribió:

> Le Thursday 07 April 2011 12:12:50 Gonéri Le Bouder, vous avez écrit :
> > 2011/4/7 Alejandro <aescanero at gmail.com>:
> > Hi Alejandro,
> >
> > (...)
>
> Hello :)
>
> > > Is possible to put a protocol url like amqps:// and send the control
> > > to a extension?
> > > Is possible to send more than one inventary or other job to more that
> > > one server?
> >
> > Do you want the agent to speak AMQP directly and drop HTTP/JSON? If so
> > do you know if it's possible to do that in Perl? Is there a AMQP
>
> yes there is libraries in perl, that must be tested ... and i'am in favour
> of talking directly AMQP.
>
> Cheers
> --
> Benoit Mortier
> CEO
> OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
> Promouvoir et défendre le Logiciel Libre http://www.april.org/
> Main developper in FusionDirectory : http://www.fusiondirectory.org/
> Contributor to OPSI : http://opsi.org/
>



-- 
Alejandro Escanero Blanco
Administrador de Sistemas GNU/Linux
Desarrollador de GOsa (http://www.gosa-project.org)
Blog: http://www.mylifebetweencomputers.com
Jabber: blainett at jabberes.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/fusioninventory-devel/attachments/20110407/759c7520/attachment-0001.htm>