Re: Introduction, XML-RPC Profile

Aaron Marsh <[email protected]> writes:

> 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.
> 
> 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'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!
> 

Cool! Did you implement the proxy/gateway as an apache module or as a 
library?

> 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).

Ah, was is other issues besides the lack of support for the dateTime 
and base64 data types?

> 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.
> 

Great work! We would love to integrate your patches into the RoadRunner 
distribution. The thing is that we (CodeFactory AB) need to have full 
copyright of source code in the RoadRunner distribution.

Great work!

/ Jonas
-- 
Jonas Borgström                  [email protected]
CodeFactory AB                   http://www.codefactory.se/
Office: +46 (0)90 71 86 14