It's transparent replacement for XMLRPC using binary format over HTTP.
XMLRPC or fastRPC is selected by negotiation in HTTP headers.
It should be faster.
It seems to have both C++ and PHP4 libs.
>
> For LS developers:
> if you would have nothing to do
>
> http://fastrpc.sourceforge.net/
>
> It's transparent replacement for XMLRPC using binary format over HTTP.
> XMLRPC or fastRPC is selected by negotiation in HTTP headers.
> It should be faster.
I'm not so sure..
if the speed gain is thought to come from the data being smaller (binary
vs. XML) - we're not sending that much data.
if it's faster to parse their binary format than XML - that might be the
case, but we'd have to measure.
and we should also simply consider trying to use a simple compression
encoding (say gzip) inside HTTP (such encodings are part of the protocol).
the FastRPC approach pretty much reminds me of WBXML (WAP Binary XML), on
which huge resources were spent. it was a similar setup: encode
WAP-related documents in binary (compact) format. but actually simply
gzipping the original XML documents gave about the same results (though
WAP Forum members didn't really like to admit to it...)