Web Remote Procedure Call (hereinafter referred to WebRPC) is not set in the pages under the premise of the remote method to call, is a recent hot and in some occasions, and he has even become an alternative way to achieve this.    WebRPC way to achieve experienced url from the ordinary reader, hidden frames, IFrame, XMLHTTP and Flash.    This paper will present the WebRpc programme (product) list, and a simple evaluation. 

  The evaluation will be conducted in the following areas: Client, server-side to achieve, whether their own package agreement, whether to support the sequence / anti-sequence, the sequence is complete support (atom type, object type), whether or not to support different Step / synchronous manner.    Note that since the Web-distance calls have not been large-scale use.    I do not have their own in the use of enterprise applications WebRPC experience, but in the entertainment applications, online games, has been very good use.    These applications have been "asynchronous message-oriented Web applications (AMOWA)" to be discussed in detail, interested in the Product Guide column can be read in this article. 

  1 MSRS (Microsoft Remote Scripting) 

  Address: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rmscpt/Html/rmscpt1.asp 

  Description: In the early Web browser limited functions.    Applet the emergence of providing a platform for the MSRS.    In this programme, MSRS category, as well as through an applet on the page parameter configuration, and server-side to cross in order to achieve a long-distance call.    Adoption of this technology will actually do not refresh pages to the work as one of the rsproxy.class not visible Applet completed.    I have seen the early adoption of this online Web chess programme.    Advantages: easy cross-browser; shortcomings: server-side Microsoft asp, applet loading slow data do not support the type of sequence / anti-serialization. 

  2 JSRS (Javascript Remote Scripting) 

  Address: http://www.blueshoes.org/en/javascript/jsrs/ 

  Description: Data Access supports two ways: HTTP GET method (dynamic loading JS), HTTP POST method (using JS Iframe create a dynamic, in which to submit a form).    Not refresh pages, the sequence of simple data support / anti-serialization. 

  3 XML-RPC 

  Address: http://www.xmlrpc.org/ 

  Description: XML-RPC defines a protocol specification, because of its lightweight, the concept of integrity, and are therefore present the vast majority of languages have achieved, including Java (Apache xml-rpc), PHP, javascript, VBScript, python, and so on.    Blog form the largest exchange agreement, management also followed XML-RPC standard.    Advantages: the vast majority of language support, simple and standardized.    Disadvantages: Java Implementation of the sequence data type limited support 

  4 dwr (Direct Web Remoting) 

  Address: https: / / dwr.dev.java.net / 

  Description: one at the appropriate time to make appropriate concept of the small things.    Xmlhttp request a transfer, the server-side use reflection to find ways to implement the corresponding results will return.    More creative, he will need for remote server-side code calls for the dynamic conversion corresponding js code can be directly in front of call.    Simple and can be used as WebRPC study entry.    Sequence data do not support the 

  5 JSON-RPC 

  Address: http://oss.metaparadigm.com/jsonrpc/ 

  Profile: A heard that the data exchange agreement JSON (JavaScript Object Notation, http://www.crockford.com/JSON/) as a basis for agreement, on the data in this call by xmlhttp send / receive requests, support the integrity of the data sequence /-sequence.    At present, jason Web framework for the use of json rpc-bottom approach. 

  6 Burlap (http://caucho.com/burlap/index.xtp) 

  Overview: There may be strange, why Burlap can also be called on the long-range agreement.    In fact, with the Hessian achieve the same way as the Burlap (binary for the former, the latter for text), the integrity of the agreement can be more than either of the above products.    At present, I have achieved the JS call Burlap service code, all long-distance calls is the most elegant way to achieve. 

  7 XINS (XML Interface for Network Services) 

  Address: http://xins.sourceforge.net/index.html 

  Description: According to the official website of the argument, SOA Java XML code_generation - complexity => XINS.    This enormous things need to define a package description files in the html before in a call.    From the exterior view, this is the most looks like the solution.    Little is known, not evaluation. 

  8 WebService, SOAP 

  Description: In addition to Microsoft, which controls a webservice.htc, mozilla also a corresponding webservice visits.    Therefore, in HTML visit webservice is feasible.    Such an agreement is too cumbersome, unless absolutely necessary, no one will be in the use of web client. 

  Client Implementation 

  Server Implementation 

  Whether its own package agreement 

  Sequence / sequence of the anti - 

  Synchronous / asynchronous mode 

MSRS

Applet

  Microsoft ASP 

  No 

  Do not support 

  Asynchronous synchronization 

JSRS

  Iframe / dynamically loaded js 

  Variety, php, java, etc. 

  No 

  Do not support 

  Synchronous 

XML-RPC

  Xmlhttp and other methods 

  The vast majority have supported language 

XML-RPC

  Support Java Implementation limited support, and does not support Custom objects 

  Asynchronous synchronization 

DWR

Xmlhttp

Java

  No 

  Weak 

  Asynchronous synchronization 

JSON-RPC

Xmlhttp

Java

JSON

  Support 

  Asynchronous synchronization 

Burlap

Xmlhttp

Java

Burlap

  Fully support 

  Asynchronous synchronization 

XINS

Xmlhttp

Java

  Is 

  Support 

  Asynchronous synchronization 

WebService

  IE used. Htc, built-in support for mozilla 

  Indefinite, followed webservice norms and SOAP protocol 

SOAP

  Support of different platforms on each expansion 

  Asynchronous synchronization