Rephrase a confusing sentence in the jsonrpc.el manual
* doc/lispref/text.texi (JSONRPC Overview): Rephrase first sentence on building JSONRPC applications.
This commit is contained in:
parent
61dbe6bab1
commit
4f230e8dd5
1 changed files with 5 additions and 5 deletions
|
@ -5179,11 +5179,11 @@ class:
|
|||
|
||||
@item A user interface for building JSONRPC applications
|
||||
|
||||
In this scenario, the JSONRPC application instantiates
|
||||
@code{jsonrpc-connection} objects of one of its concrete subclasses
|
||||
using @code{make-instance}. To initiate a contact to the remote
|
||||
endpoint, the JSONRPC application passes this object to the functions
|
||||
@code{jsonrpc-notify'}, @code{jsonrpc-request} and
|
||||
In this scenario, the JSONRPC application selects a concrete subclass
|
||||
of @code{jsonrpc-connection}, and proceeds to create objects of that
|
||||
subclass using @code{make-instance}. To initiate a contact to the
|
||||
remote endpoint, the JSONRPC application passes this object to the
|
||||
functions @code{jsonrpc-notify'}, @code{jsonrpc-request} and
|
||||
@code{jsonrpc-async-request}. For handling remotely initiated
|
||||
contacts, which generally come in asynchronously, the instantiation
|
||||
should include @code{:request-dispatcher} and
|
||||
|
|
Loading…
Add table
Reference in a new issue