欢迎大家赞助一杯啤酒🍺 我们准备了下酒菜：Formal mathematics/Isabelle/ML, Formal verification/Coq/ACL2/Agda, C++/Lisp/Haskell
Apache XML-RPC
来自开放百科 - 灰狐
（版本间的差异）
小 |
|||
| （未显示1个用户的3个中间版本） | |||
| 第1行： | 第1行： | ||
| − | Apache XML-RPC is a Java implementation of XML-RPC , a popular protocol that uses XML over HTTP to implement remote procedure calls. | + | Apache XML-RPC is a Java implementation of [[XML-RPC]] , a popular protocol that uses XML over HTTP to implement remote procedure calls. |
Version 3 of Apache XML-RPC is still compliant to the XML-RPC specification . However, the user may enable several vendor extensions are available, that greatly extend the power of XML-RPC: | Version 3 of Apache XML-RPC is still compliant to the XML-RPC specification . However, the user may enable several vendor extensions are available, that greatly extend the power of XML-RPC: | ||
| 第7行： | 第7行： | ||
* Both server and client can operate in a streaming mode, which preserves resources much better than the default mode, which is based on large internal byte arrays. | * Both server and client can operate in a streaming mode, which preserves resources much better than the default mode, which is based on large internal byte arrays. | ||
| − | == | + | ==链接== |
*http://ws.apache.org/xmlrpc/ | *http://ws.apache.org/xmlrpc/ | ||
| + | *[http://www.ibm.com/developerworks/cn/webservices/1211_zhusy_rpc/index.html XML-RPC 的 Apache 实现] | ||
| + | |||
| + | [[category:web services]] | ||
| + | [[category:apache]] | ||
| + | [[category:RPC]] | ||
2014年11月3日 (一) 02:17的最后版本
Apache XML-RPC is a Java implementation of XML-RPC , a popular protocol that uses XML over HTTP to implement remote procedure calls.
Version 3 of Apache XML-RPC is still compliant to the XML-RPC specification . However, the user may enable several vendor extensions are available, that greatly extend the power of XML-RPC:
- All primitive Java types are supported, including long, byte, short, and double.
- Calendar objects are supported. In particular, timezone settings, and milliseconds may be sent.
- DOM nodes, or JAXB objects, can be transmitted. So are objects implementing the java.io.Serializable interface.
- Both server and client can operate in a streaming mode, which preserves resources much better than the default mode, which is based on large internal byte arrays.
[编辑] 链接
分享您的观点
