Comparison with rpclib
Hello,
I've been working on rpclib, which is almost the same project as ladon, just a bit more mature from the looks of it. I'm currently working on 2.x series documentation. In the comparison section, here's what I'm going to say about ladon:
* Supports JsonRPC, JsonWSP(Author's response to the inadequacies of JsonRPC), which rpclib does not support.
* Does not support ZeroMQ (rpclib supports both client and server)
* Uses standard python tools for xml parsing (Rpclib uses lxml, due to its excellent namespace support and speed) which is good for pure-python deployments.
* Does not do input validation. (Rpclib does schema validation)
* Does not support events.
* Does not support HttpRpc (Rest-ish protocol implemented by Rpclib author)
* Does not have a Soap client.
* Rpclib uses own classes for denoting types, whereas ladon uses python callables. This lets ladon api to be simpler, but gives the rpclib api the power to have declarative restrictions on input types.
* Does not test against ws-i.org deliverables for testing soap compatibility.
I also have some questions:
1) Does it provide an api for implementing own transports and/or protocols?
2) Does it support modifying protocol & transport headers for input & output? (e.g. soap headers and/or http headers)
Maybe we could collaborate. It'd be a waste of time and effort to keep the two projects separated.
1) Would you be interested in writing interop tests for rpclib?
2) Would you be interested in contributing a JsonWSP protocol for rpclib?
3) Will you work on a soap client that parses wsdl? If so, let me know.
4) Will you work on Soap 1.2/Wsdl 2.0 spec? If so, let me know.
Also fyi, <email address hidden> a forum for soap implementors in python. You're invited to join there.
So, what do you think about rpclib compared to ladon?
Best,
Burak
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- ladon Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: