Re: Introduction, XML-RPC Profile

> 
> Hello,
> 
> Before I get too far along, let me introduce myself.  I am a developer
> for a company called "Bluefin Robotics"
> (http://www.bluefinrobotics.com/) in the US.  Yes, we really make
> submarines.

cool.

> I'm very interested in using BEEP as the core framework for a suite of
> (commercial) operator tools.  I'm impressed with the usability
> of the existing Roadrunner toolkit.  Aside from the obvious licensing
> issues, how 'healthy' is the BEEP developer community?  Are these many
> other commercial or Open Source projects using BEEP?

i think that the roadrunner implementation is currently the best 'c' language
implementation of beep. there are lists of other beep projects, etc., at
http://beepcore.org/


> I'm particularly interested in using the XML-RPC profile for my
> application.  Over the last couple of days I've developed a
> HTTP->BEEP proxy/gateway application and have started to test the
> RR-XMLRPC implementation against the Frontier XML-RPC validation suite
> (validator.xmlrpc.com).  Finally, this morning, I passed the
> validation suite!

yeah, doing xmlrpc over beep is pretty cool

 
> Completion of the validation suite required a series of patches to the
> xml-rpc module (the xml-rpc serialization/unserialization syntax was
> internally consistent, but not consistent to other implementations).
> I've also produced a "validation test server" which will complete the
> tests.  I recognize there are some commercial aspects which may need
> to be ironed out, but I'd like to start a dialog about integrating my
> patches into the Roadrunner distribution.

good luck!

/mtr