diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2021-02-20 16:32:05 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-02-20 16:33:10 -0700 |
| commit | 78b85c221ffdc6d29856266f9bf7496aa00dbc7d (patch) | |
| tree | ab0519d9d16e7ee0e4252ac88a31d3650f95ab15 /doc/pitfalls.rst | |
| parent | 987574e75dd9a9a4346a72fd6e8c5f85b64b904e (diff) | |
| download | consfigurator-78b85c221ffdc6d29856266f9bf7496aa00dbc7d.tar.gz | |
"Lisp process" -> "Lisp image"
Following the HyperSpec's glossary.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc/pitfalls.rst')
| -rw-r--r-- | doc/pitfalls.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/pitfalls.rst b/doc/pitfalls.rst index d4bcb4a..7a7bbae 100644 --- a/doc/pitfalls.rst +++ b/doc/pitfalls.rst @@ -27,7 +27,7 @@ not try to define properties and connection types programmatically, or try to dynamically rebind or flet-bind them. The reason for this restriction is that some connection types need to invoke -fresh Lisp processes on remote hosts with (local equivalents to) the function +fresh Lisp images on remote hosts with (local equivalents to) the function objects contained in properties and connections available to be called. Since function objects are not serialisable, the only way to do this is to send over the contents of your ``.lisp`` files and load the same properties and @@ -35,8 +35,8 @@ connection types into the remote Lisp. By contrast, hosts, property application specifications and deployments can be send over in serialised form. If you were to dynamically rebind properties or connection types in the root -Lisp, then connections which do not start remote Lisp processes would use your -new definitions, but connections which start remote Lisp processes would use +Lisp, then connections which do not start remote Lisp images would use your +new definitions, but connections which start remote Lisp images would use the static definitions in your ``.lisp`` files (or lack definitions altogether). This would violate the idea in Consfigurator that properties, including nested deployments, have the same meaning regardless of the |