1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
From: Lev Lamberov <dogsleg@debian.org>
Subject: Show images from /usr/share/doc/elpa-epc/
This patch changes images location to /usr/share/doc/elpa-epc/.
--- a/readme.md
+++ b/readme.md
@@ -35,12 +35,12 @@ Here is a client code.
(deferred:$
(epc:call-deferred epc 'echo '(10))
- (deferred:nextc it
+ (deferred:nextc it
(lambda (x) (message "Return : %S" x))))
(deferred:$
(epc:call-deferred epc 'add '(10 40))
- (deferred:nextc it
+ (deferred:nextc it
(lambda (x) (message "Return : %S" x))))
;; calling synchronously
@@ -61,12 +61,12 @@ use RPC::EPC::Service;
sub echo_test {
my $methods = {
-
+
'echo' => [sub {
my $args = shift;
return $args;
},"args","just echo back arguments."],
-
+
'add' => sub {
my $args_ref = shift;
my ($a,$b) = @$args_ref;
@@ -86,7 +86,7 @@ Here is the equivalent server code in em
(require 'epcs)
(let ((connect-function
- (lambda (mngr)
+ (lambda (mngr)
(epc:define-method mngr 'echo (lambda (&rest x) x) "args" "just echo back arguments.")
(epc:define-method mngr 'add '+ "args" "add argument numbers.")
)) server-process)
@@ -133,11 +133,11 @@ Let we define the words *server* and *cl
This diagram shows the API usage and the relation of processes.
-
+
### Object Serialization
-All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format.
+All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format.
Simple list structure and some primitive types can be transferred. Complicated objects, such as buffer objects, can not be serialized. The EPC stack doesn't provide transparent remote object service, that is ORB.
@@ -279,7 +279,7 @@ Here is a sample code for the EPC server
(require 'epcs)
(let ((connect-function
- (lambda (mngr)
+ (lambda (mngr)
(epc:define-method mngr 'echo (lambda (x) x) "args" "just echo back arguments.")
(epc:define-method mngr 'add '+ "args" "add argument numbers.")
)) server-process)
@@ -317,7 +317,7 @@ The EPC has a management interface for t
Executing `M-x epc:controller`, one can display the list of current established connections.
-
+
This table shows following information:
@@ -346,7 +346,7 @@ One can use following key-bind:
Displaying a method list, one can inspect the methods which are defined by the remote process.
-
+
This table shows following information:
@@ -433,11 +433,11 @@ The EPC is developed on `deferred.el` an
The EPC user should learn asynchronous programing on `deferred.el`. The components of `concurrent.el` are just internally used at `epc.el`.
-
+
Here is a diagram for the `epc.el` architecture, which diagram may be helpful for code reading of `epc.el`.
-
+
## Other Stacks
|
