Allegro CL version 10.0
Unrevised from 9.0 to 10.0.
9.0 version

Miscellaneous Functionality

This document contains the following sections:

1.0 Introduction
2.0 The fasl reader/writer
3.0 Miscellaneous extensions
4.0 Creating and using pll files
5.0 MD5, SHA*, HMAC, RC4, and other message digest support
6.0 Base64 support
7.0 Support for encryption
   7.1 Support for Blowfish encryption
   7.2 Support for rsa encryption
8.0 Support for gzip compression and decompression
9.0 PAM support in Allegro Common Lisp
   9.1 PAM conversation functions
10.0 asdf support in Allegro CL
11.0 tar support in Allegro CL
12.0 Coverage analysis in Allegro CL
13.0 Checking format forms during compilation
14.0 Heap walkers in Allegro CL
   15.1 JSON-RPC server operators and variables
   15.2 JSON-RPC client operators and variables
   15.3 JSON-RPC built-in stream transport
   15.4 JSON-RPC built-in allegroserve transport
   15.5 JSON-RPC: how to add a new transport method
   15.6 JSON-RPC: examples
   15.7 JSON-RPC: functionality index

1.0 Introduction

This document describes functionality that does not naturally fit in any of the other overview documents.

2.0 The fasl reader/writer

The functions fasl-write and fasl-read provide a mechanism for writing Lisp data and subsequently reading it back into a Lisp image. It can handle many of the common Lisp data types. It can optionally detect circularity and structure sharing in the data and recreate the same topology up to eql-ness of components. The data is written in a binary file format similar to that used for compiled Lisp files, not in ASCII.

Among the advantages of fasl-read and fasl-write over standard Common Lisp read and print functions is that data does not have to be converted to its printed representation prior to being written (that conversion takes a significant amount of time for complex objects). The main disadvantage is that the files (unlike ASCII files with printed representations of Lisp objects) are not at all portable between versions of Lisp (or even between versions of Allegro CL on different platforms or between major releases of Allegro CL).

Not all Lisp objects may be written with fasl-write (and thus are not available to be read by fasl-read). The objects that cannot be written are CLOS objects, streams, stacks, or c-allocated data (cstructs). You can use fasl-open to open a file suitable for numerous fasl-write's. (fasl-read reads all of whatever file is specified to it.)

fasl-read reads the entire contents of its argument file. However, fasl-write, if its argument is a stream rather than a filename, writes data to the stream but does not close it. Thus you can open a stream and do multiple fasl-write's to it. The stream must have :element-type (unsigned-byte 8). fasl-open opens an appropriate stream, as shown in the example.

Here is a simple-minded example to show the correct syntax and give an idea of the effect:

(excl:fasl-write '(a b #1=#:c (#1#) #*1011 #(1 2 3) 
1 1.1 1.1d0 1/2
#c(1 1) #c(1.5 1.5) "abc")
(excl:fasl-read "test.fw")

(setq f (fasl-open "test2.fw")) 
(excl:fasl-write '(a b c) f) 
(excl:fasl-write '#1=(a b . #1#) f t) 
(excl:fasl-write '#(1 2 3 4.5) f)
(close f)

(excl:fasl-read "test2.fw")

Application note

fasl-read and fasl-write require the compiler so they are not available in application images without the compiler.

3.0 Miscellaneous extensions

The table describes those extensions to Common Lisp that do not naturally fit elsewhere in the documentation. We only provide brief information in the table. Please follow the link to the documentation page for a full description.

Name Arguments Notes
excl:dribble-bug &optional file This function is an extension of the Common Lisp function dribble. dribble-bug called with the optional file calls several information functions whose output is then placed at the beginning of the dribble file. See also excl:*dribble-bug-hooks*.
excl:uncompile function-name

If the function function-name was compiled with the compile function (as opposed to having been in a file that was compiled with compile-file and subsequently loaded), then the function is `uncompiled,' i.e. its function definition is replaced by the original interpreted definition.

This function will only work when definitions are saved. See the description page for excl:uncompile and the page for excl:*save-function-lambda-expression* for details.

excl:bignump object These functions, like similar ones in standard Common Lisp return t if object is of the type specified, and nil otherwise.
excl:file-older-p file-1 file-2 If file-1 and file-2 both exist, and if file-1 is older than file-2, this function returns t. Otherwise, it returns nil.
excl:if* test-form {then then-form+ | thenret} {elseif else-test-form {then else-then-form+ | thenret}}* [else else-form+] This extension to cl:if allows symbols like then, else, elseif, and thenret in the body allowing a complex number of cases and outcomes to be specified.
excl:named-readtable name &optional errorp This function looks up a readtable by name. name must be a symbol, but it is coerced to a keyword (so readtables are named by keywords). setf may be used to associate a name to a readtable. The association can be broken by setting to nil. See also with-named-readtable.
excl:prefixp prefix sequence This function returns non-nil if sequence starts with prefix, returning the index in sequence where prefix ends (so (prefixp "foo" "foobar") returns 3). While this can be done using regular-expression matching (see regexp.htm), this function is easier to use for very simple cases.
excl:gen-sym x Similar to cl:gensym except that a symbol is accepted as the optional argument (as well as the standard string or integer), in which case the symbol-name is used. This is useful for programs that are intended for use in either ANSI or modern Lisps, where it is desired to print any gensyms without requiring escapes (see case.htm).

4.0 Creating and using pll files

A pll file can be used in association with a Lisp image. It contains constant code vectors and strings that can be shared among many Lisp objects. When an image uses a pll file and a function is compiled, the new codevector is compared to codevectors in the pll file. If a match is found, the match is used and no new codevector is allocated. Similarly, if a constant string is specified (with excl:pure-string) and a matching string appears in the pll file, no new string is allocated and the match is used. Strings in a pll file cannot be modified. Attempting to do so causes an error. (Neither can codevectors be modified but there is no user-visible way to modify codevectors as there is with strings.)

Strings and codevectors in a pll file are not also (after being garbage collected) in the Lisp heap. Thus if a string has been successfully purified, it will not be in the heap after a global gc. A total count of strings and codevectors is shown in the output of (room t).

Constant strings in pll files cannot be overwritten (constant strings stored in the heap can be overwitten although doing so is actually illegal). Strings naming Common Lisp symbols are usually stored in pll files, for example. This example shows in that case, the strings cannot be modified:

cl-user(1): (pll-file)
cl-user(2): (nstring-upcase (symbol-name 'car))
Error: Attempt to store into purespace address #x2d7865e8.
  [condition type: purespace-write-error]

Here we tried to upcase the string naming the symbol car (this is a modern Lisp where symbol names are lowercase -- see case.htm). The change failed and signaled purespace-write-error, which is the condition specific to this issue. The next example shows that modifying a constant strings not in the pll file does not signal an error:

cl-user(88): (setq teststring "this-string-is-likely-not-in-the-pll-file")
cl-user(89): (dotimes (i 4) (gc))
cl-user(90): (nstring-upcase teststring)
cl-user(91): teststring

The call to nstring-upcase is in fact illegal: you may not modify a constant, but it is an error that does not signal an error unless the string is located in the pll file.

pll files are created with the cvdcvt program described next.


Arguments: [-o outfilename] [-u] [file1 file2 …]

A .pll file, outfilename, is created holding all the unique code vectors and strings. If outfilename is omitted it defaults to code.blob.

If -u is specified, then no duplications of strings are done, otherwise for every string that has no lowercase characters in it and at least one uppercase character, a lowercase copy is added to the output file. This is the default and is useful for set-case-mode. If no files are specified, stdin is used.

.str (string) files and .cvs (code vector) files are combined without redundancies; if two files of the same extension have identical objects, the object from the file specified first to cvdcvt is retained, and the latter object is removed from the output. This allows for files (.cvs files especially) to be arranged by code vectors in order of execution, to provide for locality of reference. Those .cvs files that were produced by training techniques should be placed first in order to have the desired effect.

As said in the description, pll files are built out of cvs files and str files. cvs files are created with sys:write-codevectors and can be created by sys:flush-codevectors. str files are created with record-strings. See also record-code-vectors.

The following functions can be used to associate a pll file with an image, to find out which pll file is used with an image, and to use strings in the pll file.

Name Arguments Notes
excl:pll-file [none] Return the location of the current .pll file, or nil if there is no .pll file associated with this Lisp.
excl:use-pll-file name &key (global-gc t) Associates the current Lisp with the pll file specified by name. It is an error to associate an image already using a pll file with another pll file.
excl:pure-string x When not in the body of sys:record-strings, returns a pure-string if there is one identical to the argument and a heap-allocated string if there isn't. When in the body of sys:record-strings, also write the string to the str file being created.

5.0 MD5, SHA*, HMAC, RC4, and other message digest support

Allegro CL provides various message digest algorithms. Various algorithms are supported, including MD2, MD4, MD5, SHA1, SHA224, SHA256, SHA384, SHA512, and RMD160. Rather than have functions for each of these types, there are general functions for them, named digest-* and listed first. HMAC support is available for :md5, :sha1, :sha224, :sha256, :sha384, and :sha512. The functions hmac-init, hmac-update, hmac-string, and hmac-final implement these algorithms.

The MD*, SHA* and RMD160 functions are all are cryptographic hash functions. A hash function takes a long string (or message) of any length as input and produces a fixed-size output. This output is sometimes termed a message digest.

The keyed-hash algorithm HMAC is designed to work with algorithms MD5 and SHA* (for *=1, 224, 256, 384, and 512, to list what Allegro CL currently supports). Keyed hash algorithms work by utilizing an existing hash function (such as MD5 or SHA1) and using a secret "key" as part of the information to hash. If one party sends a message to another party and also includes an HMAC with the message, the receiver (if he/she shares the same secret key) can verify that the message hasn't been altered by running the message through the HMAC functions using the same key. If the two HMACs match, then the message is considered, with high probability, to be unaltered

RC4 is a stream cipher algorithm. It is used to encrypt streams of data.

Many of these function require SSL support (see Secuere Socket Layer (SSL) in socket.htm).

The functions available are:

General digest functions

These functions are in the :digest module loaded with (require :digest).

MD5 functions

SHA1 functions

These functions are in the :sha1 module loaded with (require :sha1).

Related utility functions

HMAC functions for MD5 and SHA*

These functions are in the :hmac module loaded with (require :hmac).

RC4 functions

These functions are in the :rc4 module loaded with (require :rc4).

6.0 Base64 support

Allegro CL provides support for Base64 encoding within Lisp. Base64 encoding is a 64-bit representation scheme that uses the ASCII characters A-Z, a-z, 0-9, + and /. Since padding could be needed in converting multiples of 8-bits into base64, = characters are used, when necessary, as padding at the end of a converted string. Base64 encoding is described in the RFC2045 document (

These functions provide the Base64 support in Allegro CL:

Here are some examples, first using integer-to-base64-string and base64-string-to-integer:

cl-user(2): (integer-to-base64-string #xfeedfacefeedface)
cl-user(3): (base64-string-to-integer "/u36zv7t+s4=")
cl-user(4): (format t "~x" *)

And now using usb8-array-to-base64-string and base64-string-to-usb8-array:

;;  The encoding results may differ between Windows and 
;;  UNIX/Linux/Mac OS X (the transcript is from a
;;  UNIX machine).

cl-user(5): (setq a (string-to-octets
                     (setq s
(defun deep-thought ()
  (sleep (years2secs 7500000))
                     :external-format (crlf-base-ef :latin1)))
#(10 40 100 101 102 117 110 32 100 101 ...)
cl-user(6): (usb8-array-to-base64-string a)
cl-user(7): (base64-string-to-usb8-array *)
#(10 40 100 101 102 117 110 32 100 101 ...)
cl-user(8): (setq a2 *)
#(10 40 100 101 102 117 110 32 100 101 ...)
cl-user(9): (equalp a a2)
cl-user(10): (octets-to-string a2 :external-format (crlf-base-ef :latin1))
(defun deep-thought ()
  (sleep (years2secs 7500000))

7.0 Support for encryption

Allegro CL provides implementations of some publicly available encryption algorithms: blowfish (see Section 7.1 Support for Blowfish encryption) and rsa (see Section 7.2 Support for rsa encryption). Please note that we make no claims about the actual security provided by these encryption schemes.

7.1 Support for Blowfish encryption

The Blowfish algorithm, described on this page (and links from it), is a high speed symmetric cryptographic algorithm (or cipher). The same key is used to encrypt and decrypt the data. Blowfish encrypts blocks of 64 bits (8 octets) at a time. The functions below can automatically pad out the data to encrypt to be a multiple of 8 octets. Blowfish was designed by Bruce Schneier, a leading authority on cryptography and author of the book Applied Cryptography. Schneier writes in his book published in 1996: "I know of no successful cryptanalysis against Blowfish."

Here are some examples of Blowfish encryption and decryption:

;; Example 1. string encrypting

cl-user(12): (blowfish-encrypt "my secret message" 
                        :key "my key")
#(57 27 110 242 191 19 182 150 1 5 ...)
cl-user(13): (blowfish-decrypt * :key "my key" :string t)
"my secret message"

;; Example 2. (unsigned-byte 8) encrypting:

;; Here we allocate an (unsigned-byte 8) array with a size 
;; that is a multiple of 8 and fill it with data.  
;; We can do in-place encryption and decryption.
;; We specify no padding (since otherwise 8 bytes of padding would
;; have to be added and there's no room in this array for that):

;; Create our array:

cl-user(12): (setq aa (make-array 8 :element-type '(unsigned-byte 8) 
                        :initial-contents '(2 4 6 8 10 12 14 16)))
#(2 4 6 8 10 12 14 16)

;; Encrypt it in place

cl-user(13): (blowfish-encrypt aa :key "my key" 
               :in-place t :pad nil)
#(129 144 108 210 20 227 10 58)

;; Verify that it has been modified:

cl-user(14): aa
#(129 144 108 210 20 227 10 58)

;; Now decrypt in place. Notice how the arguments to 
;; blowfish-decrypt match those to blowfish-encrypt:

cl-user(15): (blowfish-decrypt aa :key "my key" 
                 :in-place t :pad nil)
#(2 4 6 8 10 12 14 16)

;; And verify that the array is now back to normal:

cl-user(16): aa
#(2 4 6 8 10 12 14 16)

;; Example 3. use of contexts

;; Create context which holds the key processed by 
;; blowfish to prepare it for encryption/decryption:

cl-user(21): (setq cc (blowfish-init "my key"))
#(141 90 172 196 250 88 140 57 179 211 ...)

;; Encrypt something using the context:

cl-user(22): (blowfish-encrypt "my message" :context cc)
#(75 202 37 143 4 243 181 205 211 126 ...)

;; And now decrypt it using the same context
;; to show the original string

cl-user(23): (blowfish-decrypt * :context cc :string t)
"my message"

It is a common practice to send Blowfish keys to intended recipients using their RSA public keys. See Section 7.2 Support for rsa encryption for information on RSA encryption.

7.2 Support for rsa encryption

RSA is a public key cipher named after its inventors: Rivest, Shamir and Adleman. A public key cipher differs from a symmetric cipher like Blowfish (see Section 7.1 Support for Blowfish encryption) in two important ways:

  1. There exist two keys: the Public key and the Private key.
  2. Different keys are used for encryption and decryption.
  3. One of the keys (the Public key) can be made public without making it possible to compute the other key (the Private key).

With RSA you can encrypt with the Public key and decrypt with the Private key or encrypt with the Private key and decrypt with the Public key. Typically one encrypts with the Public key to send a message to the person with the Private key.

RSA has never been proven to be secure. However the obvious way to crack the encryption involves factoring a very large number. There is no published way of factoring a large number that's better than a brute force attempt of trying all possible factors. Thus by making the key big enough you can be sure that it won't be possible to compute the factors by brute force search in a very long time. There may be other ways to crack RSA encryption that are simply not published yet.

One major downside to RSA is that it is roughly 1000 times slower to encrypt and decrypt than a symmetric cipher like Blowfish. As a result people usually use RSA as means of transmitting a key for a symmetric cipher. For example if Alice wants to send Bob a large document securely she'll first go to Bob's web site and copy down his Public RSA key. Then she'll use a random number generator to create a 64 bit blowfish key. She'll encrypt the blowfish key with Bob's Public key and send the result to Bob. Then she'll encrypt her document using Blowfish and the key she generated. Bob will decrypt the first message from Alice using his Private RSA key. That will give him the Blowfish key he'll need to decrypt the second message from Alice.

Because the public key is known to all you have to be careful to not encrypt small values with an RSA public key since that gives you very little security. For example, suppose you decide to encrypt a 4 digit security code using an RSA public key. A person willing to steal your code need only encrypt the values 0000 through 9999 and compare them to your encrypted value to determine what the value encrypted was. If you want to encrypt a 4 digit security code XXXX then it's best to encrypt instead YYYYYYYYXXXX where the Y's are digits chosen randomly.

An RSA key pair consists of three integers: a modulus, a private exponent and a public exponent. The only number that must be kept secret is the private exponent. The public exponent is usually one of a set of common small numbers. The Allegro RSA key generator always chooses 17 as the public exponent.

An RSA key is represented in Allegro as a vector of three values:

  1. t if this is the public key, nil if this is the private key. This value is to help you distinguish one key from the other and is not used in the encryption/decryption code.
  2. the modulus value (approximately 1024 bits long).
  3. the exponent value.

RSA is a block cipher: a sequence of octets is encrypted at once. The block size isn't fixed but is usually determined by the size of the modulus. In order to encrypt data whose length is not a multiple of the block size padding is done at the end of the value and information about the padding is added to the value. The format of this padding information is not standard among rsa encryption functions, thus you can't expect any function except rsa-decrypt to be able to decrypt a value encrypted with rsa-encrypt.

The functions associated with RSA encryption and decryption are:

Because RSA encryption is resource intensive compared to symetric encoders like Blowfish, it is a common practice to encode using Blowfish and send Blowfish keys to intended recipients using their RSA public keys. See Section 7.1 Support for Blowfish encryption for information on Blowfish encryption.

Here are some examples of Blowfish encryption and decryption:

;; A call to generate-rsa-keys, such as the following, can take 
;; on the order of 10 minutes to complete. The example call
;; could have been made with ':verbose t' to get progress
;; information as it runs. 
;; The return value is a list of the public and
;; private keys, both of which are vectors.  This list
;; is made the value of the variable 'keys'.

cl-user(12): (setq keys (generate-rsa-keys :verbose nil))


;; Here we encrypt with the public key and decrypt with the private key
;; we could have encrypted with the private key and decrypted with the
;; public key as well.

cl-user(13): (rsa-encrypt "my secret message" (car keys))
#(102 136 69 180 180 27 185 63 132 137 ...)

cl-user(14): (rsa-decrypt * (cadr keys) :string t)
"my secret message"

8.0 Support for gzip compression and decompression

The inflate and deflate modules allows you to compress data as it is written to files, and to open streams to files containing gzip compressed data and to uncompress the data while reading the file. To load the modules, evaluate (require :inflate) and (require :deflate). Symbols in the modules are in the package. (There are two modules because they were added at different times.)

The :deflate module requires that the libz library be available on your computer (and in the correct version). If you do not have that library or do not have the correct version, deflation will not work. Allegro CL functionality that uses deflation (such as AllegroServe, see aserve/aserve.html) will warn that they cannot compress data but will continue to work without data compression.

The inflation function can be applied to instances of the class The function is a utility function which can be applied to an input stream to position the file position to the correct location for uncompressing.

The deflation functions,, and can be applied to instances of the class

The value of the variable sys:*zlib-system-library* is the name of the gzip library used by the deflate module.

inflate-stream and related functions




Arguments: input-stream output-stream

The compressed information from the input-stream is read and the uncompressed information is written to the output-stream.

Both streams must support (unsigned-byte 8) element reading and writing.




Arguments: input-stream

If the input stream is positioned on the header of a gzip'ed file then skip that header. input-stream is not an instance of the class It is simply an input stream (opened, for example, with open). The file position must be moved to the beginning of the compressed data before unziping, and only at that point should an instance of be created (see

If the input stream is not positioned on a gzip header then nothing is done.




The stream class for instances of files containing comressed gzip'ed data. Instances of this class are suitable as arguments to

To create an instance of this class, do the following:

  1. Make a stream (using, e.g. open) with a data source which contains compressed data.
  2. If the this file may have a gzip header on it, apply to the stream.
  3. Create an instance of by evaluating:
    (make-instance 'inflate-stream :input-handle <stream created in 1>)

    The call to make-instance will return a stream which can be read to recover the uncompressed data.

Closing the inflate-stream will also close the stream created in step 1.

deflate-stream and related functions

To write compressed data, you create a deflate-stream and at that time specify an ultimate taget, which is either a regular stream (perhaps open to a file) or a octet vector (of element type (unsigned-byte 8)). You then write data to the deflate-stream and that data is compressed and eventually written to the target. We say eventually because there is a lot of buffering so you do not see data in the target immediately. When you are done, you close the deflate-stream and that causes any remaining data to be written to the target.

Closing the deflate-stream does not close the target if it is a stream. You must close the target stream yourself.

You create deflate-streams with make-instance, as described next.




The stream class for instances of deflation streams which accepts characters and bytes and causes them to be compressed and sent to a target.

You created a deflate-stream with make-instance. You must specify a target when you create a deflate-stream.

Here is a sample make-instance call:

(make-instance 'deflate-stream :target target-spec 
                               [:compression compress-spec])

target-spec can either another stream, or it can be a vector (that is an actual stream or an actual vector). The stream must be writable. The vector must have element-type (unsigned-byte 8).

compress-spec can be :gzip (the default) or :deflate. :gzip is the preferred format as the result can be uncompressed with the (be sure to specify :skip-gzip-header t to the make-instance creating the inflate-stream or to call after the input stream is opened). The :gzip format output can also be uncompressed with the gunzip program found on Unix.

A stream as the target-spec

If you pass a stream as the target-spec then as you write characters and bytes to the deflate-stream, the bytes resulting from deflation will be written to the given stream. There is a lot of buffering going on in this stream and the compression library. Therefore you may not see the results in your target-spec stream immediately.

When you close the deflate-stream the last bytes in all the buffers will be sent through deflation and the end of deflation record will be written to the target-spec stream.

Again, the target-spec stream will not be closed when the deflate-stream is closed. It is the callers responsibility to close the stream passed in as the target-spec.

The function deflate-target-stream will return that target-spec stream used by the deflate-stream.

A vector as the target-spec

Passing a simple vector of type (unsigned-byte 8) as the target-spec is telling the deflate-stream that you wish to collect the deflation result in vectors in the lisp heap. The size of the vector passed is not important. Additional vectors will be created as necessary to hold data as it is written.

Once you have closed the deflate-stream after all data has been written to it, you can retrieve the result with or, as described in the descriptions of those functions. The deflate-stream-vector-combined combines all results into a new vector if the target vector is not large enough. deflate-stream-vector returns the vectors created by writing to the deflate-stream, along with additional information.




Arguments: deflate-stream

Returns the stream which is the target of deflate-stream which must be a deflate-stream. Returns nil if deflate-stream has a vector as its target.




Arguments: deflate-stream

deflate-stream must be a deflate-stream whose target is a vector. In that case, this function returns three values:

  1. The newest vector created so far by writing to deflate-stream (or the last such vector if deflate-stream is closed).
  2. The number of bytes of actual data in the newest vector.
  3. A list of previous vectors holding data in reverse order.

For example, if the three returns values are:

    (c b a)

then the deflated result is found by combining in this order:

    all of a
    all of b
    all of c
    the first 100 bytes of v

This function signals an error if deflate-stream has a stream as its target.




Arguments: deflate-stream

deflate-stream must be a deflate-stream whose target is a vector. In that case, this function returns two values:

  1. An octet vector.
  2. The number of bytes of actual data.

The octet vector is newly created if necessary (if the target vector specified when the deflate-stream was created is not large enough to hold the compressed data).

This function signals an error if deflate-stream has a stream as its target.


Suppose we wish to create a compressed file from the following text:

;; file begin
(in-package :user)

(defpackage :foo (:use :cl :excl))
(defun foo (y) (bar y))

;; file end

In the following transcript, we use a deflate stream to create and then we inflate by opening the file, stripping the gzip header, creating an inflate-stream instance, reading the file line by line, closing the inflate-stream, and closing the file. We could also inflate the while file by calling inflate.

;; We load the modules and then write a compressed file.
;; Once it is written, we read it back uncompressing it.

cl-user(61) (require :deflate)
; [loading messages]
tcl-user(62) (require :inflate)
; [loading messages]
cl-user(63): (setq myfile (open "" :direction :output :if-exists :supersede))
#<file-simple-stream #P"" for output pos 0 @ #x100439f9f2>
cl-user(64): (setq *df* (make-instance 'deflate-stream :target myfile))
#<deflate-stream in 0 / out 0 @ #x10043ad922>
cl-user(65): (format *df* ";; file begin~%~%")
cl-user(66): (format *df* "(in-package :user)~%~%")
cl-user(67): (format *df* "(defpackage :foo (:use :cl :excl))~%")
cl-user(68): (format *df* "(defun foo (y) (bar y))~%~%")
cl-user(69): (format *df* ";; file end")
cl-user(70): (close *df*)
#<deflate-stream in 120 / out 106 @ #x10043ad922>
cl-user(71): (close myfile)
cl-user(72): (setq s (open "" :direction :input))
#<file-simple-stream #P"" for input pos 0 @ #x1004400732>
cl-user(73): ( s)
cl-user(74): (setq is
              (make-instance ' :input-handle s))
  inflating #<file-simple-stream #P"" for input pos 10 @
              #x1004400732>ef :latin1-base, in: 0, inflated 0, used: 0 of
  @ #x1004417412>
cl-user(75): (read-line is nil s)
";; file begin"
cl-user(76): (read-line is nil s)
cl-user(77): (read-line is nil s)
"(in-package :user)"
cl-user(78): (read-line is nil s)
cl-user(79): (read-line is nil s)
"(defpackage :foo (:use :cl :excl))"
cl-user(80): (read-line is nil s)
"(defun foo (y) (bar y))"
cl-user(81): (read-line is nil s)
cl-user(82): (read-line is nil s)
";; file end"
cl-user(83): (read-line is nil s)
#<file-simple-stream #P"" for input pos 98 @ #x1004400732>
cl-user(84): (close is) ;; this also closes s.


The source code to the gzip utility is included with the Allegro CL distribution, in [Allegro directory]/src/

9.0 PAM support in Allegro Common Lisp

PAM stands for Pluggable Authentication Modules. It is a flexible mechanism for authenticating users. An Allegro CL module provides a Lisp wrapper around the PAM API on Linux, Solaris, and some other unixlike operating systems. We do not discuss PAM in detail here. See

PAM is supported on the following platforms:

PAM is not supported in Allegro CL on the following platforms:

The PAM API is is loaded by evaluating (require :pam). Symbols naming functionality are in the util.pam package. Depending on your system configuration, your program may be required to run with 'root' privileges to successfully make use of PAM.

There is one class and several operators defined in the pam module. They are:



Package: util.pam

The class of pam objects. A pam object is created by pam-start.



Package: util.pam

Arguments: service-name user &key conversation data

This function provides a wrapper around the pam_start(3) PAM library function. service-name should be a string naming the desired PAM service. user may be nil or a string.

If conversation is specified, it should be a function (or a symbol naming a function) which will perform the PAM "conversation", when necessary. data is optional user-defined data that will be passed to the conversation function. If conversation is nil (the default), a default conversation function will be used. For more information on conversation functions, see Section 9.1 PAM conversation functions.

This function returns a pam object on success. You will pass this object to other functions and methods. If pam-start fails, an error is signalled.


Generic Function

Package: util.pam

Arguments: pam &optional status

The default method is analogous to the pam_end(3) PAM library function. pam must be a pam object returned by pam-start. If status is specified, it should be an integer. See the pam_end(3) description (in PAM documentation not supplied here) for details on the use of status. If status is nil, excl.osi:*pam-success* will be used.

This method returns t on success, otherwise it signals an error.



Package: util.pam

Arguments: (var &rest rest) &body body

with-pam is a convenience macro which evaluates body with var bound to the result of calling pam-start with the arguments specified in rest. pam-end will be called when body terminates, either normally or abnormally.

Sample use

(util.pam:with-pam (pam "login" "jimmy")
  (format t "This is the body~%"))


Generic Function

Package: util.pam

Arguments: pam &key flags password

This default method is analogous to the pam_authenticate(3) PAM library function. pam must be a pam object returned by pam-start. If password is specified, it should be a string. It will be used when needed if the default conversation (see pam-start) is used. If flags is specified, it should be an integer.

On success, this function returns t.

If the call is not successful, the function returns two values, nil and a status value. The status value will be a keyword or an integer. Possible status value keywords are:

If pam_authenticate(3) returns an unrecognized status code, it will be returned without being converted to a keyword.


Generic Function

Package: util.pam

Arguments: pam microseconds

This method is used to request a delay of at least the specified number of microseconds (which must be an integer) before returning from an unsuccessful pam-authenticate call. Setting a delay slows down attempts to rapidly try different passwords for an account.

If multiple calls to set-pam-fail-delay are made, the largest requested delay will be used. On some systems, it is possible that the PAM modules themselves may request delays, so you might notice a delay longer than one you requested (and in particular, you might notice a delay even though you hadn't called set-pam-fail-delay).

The actual delay will is computed pseudorandomly and may differ by as much as 25% above or below the maximum requested value.

Regardless of the success or failure of a pam-authenticate call, the delay is set back to 0 before returning from pam-authenticate. This means that you should generally call set-pam-fail-delay before each call to pam-authenticate.

9.1 PAM conversation functions

The default conversation function will display prompts and request input from *terminal-io*. If the password argument is supplied to pam-authenticate, it is probable that no interaction with *terminal-io* will occur at all. However, if your system configuration or application has different requirements, you can provide your own conversation function.

The conversation function will be called by the PAM API when it needs to collect information to move the authentication process along.

If you supply your own conversation function, it should accept two required arguments, and one keyword argument:

Arguments: messages data &key password

messages will be a list of pam-message structures. data will be the same value that was supplied to pam-start. password will be the password that was passed to pam-authenticate (and may possibly be nil).

The conversation function should return a list of pam-response structures. The list must have the same length as the messages list. The first entry in the list should be the response that corresponds to the first message. The second entry should correspond to the second message, and so forth. See pam_conv(3) for details.

The pam-message structure has two slots, style and message. The style slot will be one of the following keywords (:prompt-echo-off, :prompt-echo-on, :error, :text) or an integer (indicating an unrecognized style). message will be a string which may be used to prompt the user.

The pam-response structure has two slots, response and code. response should be a string with the data requested by the corresponding message. code should be an integer (the default is 0). Again, see pam_conv(3) for details.

10.0 asdf support in Allegro CL

The popular system definition facility, asdf, is included with Allegro CL. Evaluate (require :asdf) to load it into a running Lisp. See [Allegro directory]/code/asdf.readme for more information, [Allegro directory]/code/asdf.license for the license, and [Allegro directory]/src/asdf.lisp for the source code. asdf documentation can be found on the web at

11.0 tar support in Allegro CL

Allegro CL provides support for extracting contents from tar files. To use this facility, evaluate

(require :tar)

The tar functions are named by symbols exported from the util.tar package.

The tar functions take streams (rather than pathnames) as arguments. util.tar:list-tar lists the contents of the tar file. util.tar:extract-tar extracts the contents into a specified directory.

Here are example forms using the tar functions:

(with-open-file (s "foo.tgz")
  (util.tar:list-tar s :gzip t))
(with-open-file (s "foo.tgz")
  (util.tar:extract-tar s :gzip t :directory "tmp/"))



Package: unknown

Arguments: stream &key gzip

List, to *terminal-io*, the contents of stream, which should be a stream opened to a tar file. If stream is compressed with gzip compression, specify a non-nil value for gzip. bzip2 compression is not supported.



Package: unknown

Arguments: stream &key gzip directory verbose

Extract, to directory, the contents of stream, which should be a stream opened to a tar file. If stream is compressed with gzip compression, specify a non-nil value for gzip. bzip2 compression is not supported.

directory defaults to nil, which means extract to the current directory (as returned by current-directory).

If verbose is specified non-nil, information about what is being done will be printed.

12.0 Coverage analysis in Allegro CL

When testing a program, the coverage is a measure of how much of the source code has actually been tested: have all branches of a conditional been taken, have all defined functions been called, have all error handlers been triggered, and so on (coverage is described in Wikipedia here).

Allegro CL has a macro, with-coverage, which executes code and when done, prints information about how well a specified list of functions are excercised. The type of coverage, following the description in the Wikipedia article linked to above, is statement coverage, where "lines of code" is understood to mean Lisp S-expressions.

See the with-coverage page for further details and an example. Note that source file recording must be on for the coverage tool to work.

13.0 Checking format forms during compilation

Allegro CL has a facility for checking format forms during compilation. What is checked is whether there seem to be sufficient arguments in the form for the format control string to be processed without error when the form is evaluated at run time. If enabled, the facility will warn when it detects that there are two few arguments, note when there are too many arguments, and note when the control string is too complex for analysis. (Having too many argument is not an error and is indeed explicitly permitted by the ANS. However, if it is not what is intended, it is useful to know that it has happened.)

The analysis will occur when the comp:verify-format-argument-count-switch is non-nil and not 0. This switch differs from most compiler switches in that its value can be 0, 1, 2, 3, or 4 as well as nil (equivalent to 0) and t (equivalent to 2).

Here is the behavior for the various values of the switch:

Statistics are only kept if the value of the variable *format-arg-count-stats* is a list of six fixnums (representing all, missing args, args equal in number to needed, args more than needed, too complex, and syntax error). These numbers are incremented appropriately as format forms are analysed. Warnings and compiler-notes are printed if the switch value calls for them. The function format-arg-count-stats prints the collected statistics.

14.0 Heap walkers in Allegro CL

A heap walker is a tool which examines the Lisp heap and gathers information about it. The Lisp heap is where most Lisp objects are stored. It comprises the old space and new spaces described in the garbage collection document gc.htm.

The two built-in tools which walk the heap are get-objects and get-references. Each returns a heapwalk vector. This is a simple vector with element type t, whose size depends on the number of objects found. The first element of a heapwalk vector is the integer number of objects of interest found). These objects are stored in the vector elements after the first. The actual size of the vector is a little bit bigger than strictly necessary to allow for including objects created while the heap is being examined. Note that the heapwalk vector itself is an object in the heap. It is persumably not an object of interest (it did not even exist when get-objects or get-references was called) so its existence can skew the results slightly but unavoidably.

The function get-objects takes a code as its required argument and has keyword agguments old and new. The keyword arguments default to t. If specified nil, that particular space will not be searched. The code is the type code of a lisp object.

Type codes are shown in room output and also by the function print-type-counts. (Neither lists all possible type counts, just those for which at least one object of the particular type exists.) Here is a (slightly truncated) output of (room t):

cl-user(2): (room t)
area area  address(bytes)        cons         other bytes
  #  type                   8 bytes each
                             (free:used)      (free:used)
     Top #x20d7a000
     New #x20994000(4087808)   916:15225     843936:3035024
     New #x205ae000(4087808)    -----            -----
   0 Old #x20000aa0(5952864)   711:78771    2098888:3209704
Root pages: 126
  Lisp heap:    #x20000000  pos: #x20d7a000 resrve: #x20fa0000
Aclmalloc heap: #xa0000000  pos: #xa0048000 resrve: #xa00fa000
 Pure space:    #x1f8ec000  end: #x1ffff888

code   type                                 items     bytes 
126: (simple-array (unsigned-byte 16))       10767   2153400 31.4%
112: (simple-array t)                         8891   1445976 21.1%
  1: cons                                    93996    751968 11.0%
  7: symbol                                  20360    651520  9.5%
  8: function                                 9681    602864  8.8%
133: sv-vector                               20549    340840  5.0%
120: (simple-array fixnum)                     259    270272  3.9%
119: (simple-array code)                       367    192064  2.8%
117: (simple-array character)                 2396    148960  2.2%
125: (simple-array (unsigned-byte 8))           19     98720  1.4%
 12: standard-instance                        3900     62400  0.9%
  9: closure                                  2897     50432  0.7%
 15: structure                                1159     47856  0.7%
127: (simple-array (unsigned-byte 32))          11     12744  0.2%

 total bytes = 6856032
aclmalloc arena:

Now we call get-objects on type code 127, which is (simple-array (unsigned-byte 32)). There are eleven such objects, according to the list printed by room (code 127 is the last item before the list is truncated).

cl-user(3): (get-objects 127)
#(11 #(255 65535 16777215 4294967295) #(32 8224 2105376 538976288)
  #(3960924350 2165561044 562617442 2270225120 1264129478 758582028 172407450
    2782512936 595962478 1609675396 ...)
  #(0 2567483615)
  #(546914304 4087808 916 15225 529448960 536869000 553254912 536870912 843936
    3035024 ...)
  #(3960924350 2165561044 562617442 2270225120 1264129478 758582028 172407450
    2782512936 595962478 1609675396 ...)
  #(3960924350 2165561044 562617442 2270225120 1264129478 758582028 172407450
    2782512936 595962478 1609675396 ...)
  #(200235464 1375865383 2472949741 3729159793 443451277 421802134 4188904507
    2175392005 408067652 1254986169 ...)
  #(3960924350 2165561044 562617442 2270225120 1264129478 758582028 172407450
    2782512936 595962478 1609675396 ...)
cl-user(4): (length *)

The result is a heapwalk vector. The first element is 11, the number of objects of the type of interest. Then those eleven objects. Then some extra elements (19 extra in this case, for a total vector size of 31).

Once you have objects of a particular type, you can find references to that object with get-references, which returns a heapwalk vector filled with objects in the Lisp heap or in lispstatic space which point directly to the object of interest. Note that compound structures might not point to the object directly; for example, if a list has an element within it, the first call to get-references will return only the cons cell whose car is that object; you would have to repeat the get-references on that cons cell to find the cons whose cdr points to it, and so on backward through the list until you find a recognizable structure, symbol, or function that points to the head of the list. The stack can be included in the search if the include-stacks keyword argument to get-references is specified true.

Heapwalker vectors themselves point to lots of objects but are not what you are looking for when you search for references. Therefore, heapwalk vectors are marked and are not included in get-references output.

When using get-references, note the following:


This functionality in the JSON-RPC module was added as a patch in December, 2015. You must have that patch in order to use this module. See sys:update-allegro for information on getting patches.

The JSON-RPC module depends on the ST-JSON open source module. A compiled version of the module, the file st-json.fasl is included with the Allegro CL distribution and can be loaded with (require :st-json). You can download the sources and documentation from github at ST-JSON is a 'Common Lisp library for encoding and decoding JSON values (as specified on' (quoting from the ST-JSON home page). In what follows, we assume that module has been downloaded and loaded in Allegro CL. The symbols in the ST-JSON module (useful for manipulation JSON objects) are in the st-json package.

JSON-RPC is lightweight remote procedure call protocol similar to XML-RPC. (See xml-rpc.htm for information on the XMP RPC interface in Allegro CL.) The JSON-RPC module in Allegro CL provides an API within Lisp to JSON-RPC.

Package and module loading

Symbols naming functionality in the module are in the net.json.rpc package. You load the module with the following require form:

   (require :json-rpc)

The JSON-RPC module is initialized with the following function.



Package: net.json.rpc

Arguments: &key client server converter methods global

This function initializes various JSON-RPC features. The various keyword arguments are described in later sections as they apply to client or server operations.

The converter keyword must be omitted, nil, :default, or a function of one argument. If omitted or nil, there is no effect.

When a function is specified, it must be a function that transforms a string (denoting a JSON method or member name) to a corresponding Lisp symbol, or Lisp symbol to a corresponding JSON name string. This function is used in all cases where derived-symbol or derived-string is specified.

The value :default specifies a built-in function with the following behavior. This is the initial setting as well.

Convert a string to a symbol or a symbol to a string using simple case and hyphenation ruled:

       "fooBarBaz"  <-->  foo-bar-baz

This function will try to signal a warning when troublesome cases are found.

For servers

A non-nil   server keyword argument specifies a default transport protocol for JSON-RPC servers. If the global argument is nil, the only effect is to perform any initialization required for the transport protocol (such as loading a required fasl or library). If the global argument is non-nil (the default) then any running JSON-RPC servers are stopped.

When the methods keyword argument is non-nil, all current JSON-RPC method definitions are deleted, and any desired methods must be defined again by evaluating or loading the defining forms.

For clients:

A non-nil   client argument specifies a default destination for client calls. If the global argument is nil, the only effect is to perform any initialization required for the transport protocol (such as loading a required fasl or library). If the global argument is non-nil, the value of *json-rpc-destination* is updated.

15.1 JSON-RPC server operators and variables



Package: net.json.rpc

Arguments: name bv &body body

Defines a Lisp function that can be dispatched as the destination of a JSON-RPC message to the server. The arguments are:

name: the value can be

options: options may only be specified using the list value for name. The options can name a set or sets in which to include the method. If no set is named, the method is part of all sets.

The bv argument: the value should be a list of one of the following forms:

([var]... [&rest tailvar] [&whole listvar])

The "params" member in the JSON message must be a JSON array. Each var specifies a required element in the array, and is bound in body to the corresponding array element.

If &rest is present, additional arguments are allowed in the array, and the list is bound to this tailvar. By-position methods are dispatched by matching all methods without &rest first, then all methods with &rest. All methods are matched in order of decreasing number of required args.

(&key [label]... [&allow-other-keys] [&whole wholevar])

The "params" member in the JSON message must be a JSON object. Here:

      label --> (var member-name)
	    --> symbol == (symbol derived-string)
	    --> string == (derived-symbol string)

Each var is a keyword argument bound in body to the named member of the object. If &allow-other-keys is present, additional members are ignored; they are accessed by the member name from the pointer bound to wholevar.

By-name methods are dispatched by matching methods without &allow-other-keys first.

In each group, the methods are ordered by decreasing number of required members. The member names are sorted lexicographically and the signatures are sorted lexicographically within each set of equal length.

The dispatch strategy may cause some methods to be unreachable. Some unreachable methods may be detected at compile time, others may not.

body returns one value, a JSON object or a Lisp object that is converted to JSON by default rules, or the body signals an error that is returned as a JSON error object.

The same JSON method name may apply to several actual methods with distinct signatures; the Lisp names of these methods must be distinct (therefore only one can be a derived name).



Package: net.json.rpc

This variable specifies the behavior when def-json-rpc-method redefines a JSON-RPC method or a one of the Lisp functions associated with the method. The value can be:

The initial value is :warn.



Package: net.json.rpc

Arguments: &key transport export receive send &

Start a JSON-RPC server, or enhance an existing server with JSON-RPC features.

The transport argument specifies how JSON-RPC messages will arrive. The format of the argument depends on the nature of the transport.

The inital implementation supports a simple stream or a web server running AllegroServe. The default for this argument can be specified with init-json-rpc. Additional arguments are interpreted by specific transport implementations.

The receive argument must be a list that specifies the JSON-RPC versions accepted by the server. The first entry in the list is the default reply version. The initial value is (:2.0 :1.0 :batch). The entry :batch specifies that batch requests will be honored.

The send argument specifies the version of reply messages. The value :same specifies that the reply message will be the same version as the request message.

The export argument is a string or symbol or a list of strings and/or symbols. A symbol denotes a Lisp function defined with def-json-rpc-method, or a set of methods specified with the :rpc-set option; if a symbol denotes both a set and a function, the set definition prevails. A string denotes a JSON-RPC method (in that case all Lisp names are included).

This function returns an object that can be used as the argument to stop-json-rpc-server.

Simple stream transport:

The transport argument must be :stream or a list (:stream stream-instance). If the argument is :stream, then a stream-instance must be specified with a :stream keyword argument. The stream-instance must be subclass of dual-channel-simple-stream.

AllegroServe transport:

The transport argument must be :aserve or a list (:aserve . aserve-start-options).

Additional transport protocols may be defined in the future.



Package: net.json.rpc

Arguments: &key server

Stop a server. The server argument should be the return value of the call to start-json-rpc-server that started the server.

See the description of init-json-rpc for information on initializing JSON-RPC for servers. A non-nil server keyword argument to that function specifies a default transport protocol for JSON-RPC servers. If the global argument is nil, the only effect is to perform any initialization required for the transport protocol (such as loading a required fasl or library). If the global argument is non-nil (the default) then any running JSON-RPC servers are stopped.

When the methods keyword argument to that function is non-nil, all current JSON-RPC method definitions are deleted, and any desired methods must be defined again by evaluating or loading the defining forms.

15.2 JSON-RPC client operators and variables



Package: net.json.rpc

A destination where JSON-RPC call messages can be sent, such as a URL.



Package: net.json.rpc

The default version for method calls from a client. The initial value is :2.0.



Package: net.json.rpc

Arguments: method-name json-parameters &key notification id destination version &

Call the server at destination with a JSON-RPC message where method-name is the method member and json-parameters is the parameters member.

Default destination is *json-rpc-destination*. Default version is *json-rpc-call-version*.

The id argument is used only in the scope of a with-json-rpc-batch expression. It specifies an id value that can be used in the call to json-rpc-batch-result.

Additional keywords are interpreted or ignored by methods specific to a particular destination.

Within the call body of a with-json-rpc-batch, the returned value is the unique JSON-RPC call id. In other contexts, the returned value is the JSON-RPC result. When notification is non-nil, no value is returned in either case.



Package: net.json.rpc

Arguments: name bv &key destination version notification id

This macro defines a Lisp function that will make a JSON-RPC call to a JSON-RPC method.

name: the value can be

The bv argument: the value should be a list of one of the following forms:

([var]... [&rest rvar])

The Lisp function expects arguments that get sent as a single JSON array. The argument names are ignored.

(&key label...  [&optional label...])

The Lisp function expects keyword arguments that are sent as members of a JSON object. The labels before &optional specify required keyword args. The trailing labels specify optional keyword args. (We ask the reader to excuse this deviant usage of the &optional marker)

      label --> (keyword-name member-name)
	    --> symbol == (symbol derived-string)
	    --> string == (derived-symbol string)



Package: net.json.rpc

Arguments: bv options callbody &rest body

Call several JSON-RPC methods as a single batch call. The options are passed to methods specific to the destination.

The variables in bv are bound and visible in callbody and in body.

The callbody expression is evaluated first for its side-effects, and then any values are discarded. Any JSON-RPC calls during this evaluation add to the content of a batch; the calls themselves do not return a JSON result, instead, they return the unique JSON-RPC id of the call in the batch. The calls in the batch are sent when the progn exits.

The expressions in body are evaluated as a progn after the result of the batch call have arrived. Within body, the function json-rpc-batch-result can be called to extract the result of a specific call.



Package: net.json.rpc

Arguments: id

When called in the body of a with-json-rpc-batch expression, this function returns the result of the request with the specified id. The id argument can be the unique id returned in the callbody of the with-json-rpc-batch expression, or the local id specified in the JSON-RPC call.

When init-json-rpc is called with a non-nil client argument, it specifies a default destination for client calls. If the global argument is nil, the only effect is to perform any initialization required for the transport protocol (such as loading a required fasl or library). If the global argument is non-nil, the value of *json-rpc-destination* is updated.

15.3 JSON-RPC built-in stream transport

Application program must supply a stream to the server or the client. The stream must be a dual-channel-simple-stream instance such as a socket or a pipe stream.

In a call to start-json-rpc-server, the value of the transport keyword argument must be :stream or a list (:stream stream). An additional stream keyword argument is accepted (so the stream to be used may be part of a list value of transport or separately specified as the value of stream argument). The stream must be a dual-channel-simple-stream instance.

In a call to call-json-rpc-method, the value of the destination argument must be a stream.

15.4 JSON-RPC built-in allegroserve transport

To use the JSON-RPC module with AllegroServe, you must load the :json-rpc-aserve module:

(require :json-rpc-aserve)

In calls to start-json-rpc-server, the transport argument must be either :aserve or the dotted list (:aserve . start-arguments) or a net.aserve:wserver instance.

Additional accepted keyword arguments include:

:url "/json-rpc"   
:content-type "text/html"
:publish additional-publish-args

In a call to call-json-rpc-method, the value of the destination argument must be a uri string or a net.uri:uri instance.

15.5 JSON-RPC: how to add a new transport method

The steps for adding a new transport method are:

  1. Choose a new keyword to identify the method.
  2. Define a subclass of json-rpc-server.
  3. Push the entry (keyword class-name) onto *json-rpc-transports*.
  4. When the method is loaded, maybe setq *json-rpc-transport* to the keyword (or a list starting witht he keyword). This is used as the default transport argument to start-json-rpc-server.
  5. Define a method for start-json-rpc-server-implementation specialized on the new server class, to initialize the server and instance. The server calls json-rpc-dispatch when it has parsed a complete JSON-RPC request. The result is nil, or a fully formed JSON-RPC reply message. If the result is nil, the message was a notification or an array consisting entirely of notifications; in that case the server does nothing. If the result is not nil, the server must send the reply message to the client; the ST-JSON package includes several methods to serialize a JSON object for transmission if the transport method uses characters.
  6. Define a method for json-rpc-stop-transport.
  7. Define a distinct type for client destination. Reserved types are string, uri, and stream.
  8. Define a method for json-rpc-send-message specialized on that type.

As an example, this very trivial implementation assumes the client and server are in the same address space:

(defclass local-server (json-rpc-server) ())
(push (list :local 'local-server) *json-rpc-transports*)

(defmethod start-json-rpc-server-implementation 
     ((server local-server) &key &allow-other-keys)

(defmethod json-rpc-send-message ((server local-server) message notification)
   (declare (ignore notification))
   (json-rpc-dispatch server message)

Here are the descriptions of some of the needed functionality.



Package: net.json.rpc

This class used in defining a new transport method. This class must be a superclass of any new transport server.



Package: net.json.rpc

This variable is used in defining a new transport method. The value of this variable is a list of the form

((transport-keyword name-of-server-class) ... )

Additional entry formats may be defined in the future.



Package: net.json.rpc

This variable is used in defining a new transport method. The value of this variable is the default transoprt method for JSON-RPC calls. This must be a transport name keyword or a list beginning with such a keyword. The tail of the list contains additional transport-specific arguments.


Generic Function

Package: net.json.rpc

Arguments: server &rest options &key &

This method must be implemented when defining a new transport method. Keyword arguments provide transport-specific inital values. This method is called after the server instance is created and initialized at the json-rpc-server level.


Generic Function

Package: net.json.rpc

Arguments: server

This method must be implemented when defining a new transport method. This method is called before any generic json-rpc-server shutdown operations are performed.


Generic Function

Package: net.json.rpc

Arguments: destination message notification &rest options &key &

This method, specialized on a new destination type, must be implemented when defining a new transport method. The message argument is a jso instance formatted for the specified JSON-RPC version. The notification argument is t for a notification or for a batch consiting entirely of notifications.

The options argument will contain all the options specified in the call to call-json-rpc-method.



Package: net.json.rpc

Arguments: server message

This function is called from the body of a start-json-rpc-server-implementation method for a new transport method. The server argument is the server argument passed to this method, and the message argument is a parsed JSON-RPC message received by the server.

This function returns nil if the message was a notification or an array consisting entierly of notifications. Otherwise, this function returns a JSON-RPC reply object that contains the result(s) of the message.

15.6 JSON-RPC: examples

To call a method with positional args to add two numbers:

;; Server def:

(def-json-rpc-method "adder" (x y) (+ x y))

;; Client call:

(call-json-rpc-method "adder" (list 2 5)) 
;; ==> 7

The client can also define a Lisp function that makes this call

(def-json-rpc-call (json-add "adder") (x y))

(json-add 2 5) 
;;  ==> 7

To call a json-rpc method with named args:

;; Server def:

(def-json-rpc-method "combineMembers" (&key (p1 "part1") (p2 "part2"))
    (jso "combined" (append p1 p2)))

;; Client call:

(setq r (call-json-rpc-method "combineMembers"
     (jso "part1" (list 2 4) "part2" (list 6 8))))
;;  ==> jso instance
(getjso "combined" r) 
;;  ==> (2 4 6 8)

;; or

(def-json-rpc-call (jappend "combine-members")
        (&key (m1 "part1") (m2 "part2")))

(setq r (jappend :m1 (list 2 4) :m2 (list 6 8)))
(getjso "combined" r) 
;; ==> (2 4 6 8)

15.7 JSON-RPC: functionality index

Copyright (c) 1998-2015, Franz Inc. Oakland, CA., USA. All rights reserved.
Documentation for Allegro CL version 10.0. This page was not revised from the 9.0 page.
Created 2015.5.21.

Allegro CL version 10.0
Unrevised from 9.0 to 10.0.
9.0 version