3 \setlength{\parindent}{0pt}
4 \setlength{\parskip}{6pt plus 2pt minus 1pt}
7 =========================
8 Protobufs for Common Lisp
9 =========================
12 :Description: Protobufs for Common Lisp
13 :Author: Scott McKay <swmckay@gmail.com>
14 :Date: $Date: 2012-08-31 11:13 -0500 (Fri, 31 Aug 2012) $
19 1.1 Implementation notes
21 2 Defining a Protobufs schema
22 2.1 .proto file to Lisp conversion
23 2.2 CLOS classes to .proto conversion
24 2.3 Using .proto files directly
25 2.3.1 A note on Lisp packages
26 2.4 Using the Protobufs macros
28 2.4.2 Protobufs service stubs
29 3 Serializing and deserializing
33 4.1 Extensions functions
34 4.2 Initialization functions
35 4.3 Python compatibility functions
36 5 Lisp-only extensions
43 The Common Lisp Protobufs library provides a fully in-Lisp way for
44 Common Lisp programs to use existing, or define new Protobufs
45 "schemas", and serialize and deserialize objects to and from the
46 Protobufs wire and text formats.
48 To use it, first load the ASDF declaration file ``protobufs/cl-protobufs.asd``
49 and then use ASDF to load the library named ``:cl-protobufs``.
55 The Protobufs library defines a set of model classes that describes a
56 protobufs "schema" (i.e., one .proto file). These classes describe a
57 schema, its options, enums and enum values, messages and fields, and
60 Unlike the 'protobuf' library described at ``http://common-lisp.net/project/protobuf``,
61 this implementation is entirely written in Common Lisp. It provides
62 some things that the 'protobuf' library does not, in particular,
63 the ability to define Protobufs schemas entirely within Lisp and
64 the ability to "export" a set of CLOS classes as a Protobufs schema.
66 The library provides the means to convert several kinds of inputs into
67 the Protobufs models, including:
69 - Parse an existing .proto file into a set of model objects.
70 - Convert a set of related CLOS classes into a set of model objects.
71 - Compile a ``proto:define-schema`` macro call into a set of model objects.
73 It also provides two ways to convert the model objects into outputs:
75 - Print a set of model objects using the standard Protobufs v2 syntax.
76 - Print a set of model objects using the Common Lisp syntax, defined below.
78 There are two formats for serialization and deserialization:
80 - The wire format, which is compact and fast.
81 - The text format, which is human readable.
83 Finally, there is a validator that takes an old version of a Protobufs
84 schema and a new version of the same schema and generates a set of
85 warnings that describes any incompatibilities between the old schema and
94 proto:protobuf-schema [Class]
96 The class the represents a Protobufs schema, i.e., one .proto file.
97 It has slots for the name, options, enums, messages and services. The
98 name is equal to the name of the .proto file, without the file type.
102 proto:protobuf-option [Class]
104 The class that represents a Protobufs option.
105 It has slots for a key and a value.
109 proto:protobuf-enum [Class]
111 The class that represents a Protobufs enum type.
112 It has slots for the enum name and its values.
116 proto:protobuf-enum-value [Class]
118 The class that represents one value in a Protobufs enum type.
119 It has slots for the value name and the value index.
123 proto:protobuf-message [Class]
125 The class that represents a Protobufs message.
126 It has slots for the name, options, nested enums and messages, and fields.
130 proto:protobuf-field [Class]
132 The class that represents one field in a Protobufs message.
133 It has slots for the name, type, index and options.
137 proto:protobuf-service [Class]
139 The class that represents a Protobufs service.
140 It has slots for the name, options and methods.
144 proto:protobuf-method [Class]
146 The class that represents one method description in a Protobufs service.
147 It has slots for the name, input type, output type and options.
150 Defining a Protobufs schema
151 ===========================
153 There are several ways to define a Protobufs schema: convert a .proto
154 file to a .lisp source file and then use the Lisp file; convert a set
155 of Lisp classes to a Protobufs model, and then use either the .lisp or
156 the .proto representation of the model; use a .proto file directly in
157 an ASDF system; or use the Protobufs macros in a Lisp source file.
160 .proto file to Lisp conversion
161 ------------------------------
163 If you have an existing .proto source file that you would like to
164 convert to Lisp classes (more precisely, to the macros defined by the
165 Protobufs library), you can use ``proto:parse-schema-from-file`` to
166 read the .proto file and then use ``proto:write-schema`` to write a
167 new .lisp file. (This is what that ASDF module type ``:protobuf-file``
172 proto:parse-schema-from-file (pathname [Function]
173 &key name class conc-name)
175 Parses the contents of the file given by *pathname*, and returns the
176 Protobufs model (a set object objects rooted at ``proto:protobuf-schema``)
177 corresponding to the parsed file. The name of the Protobufs schema is
178 generated automatically from the file name.
180 *name*, *class* and *conc-name* are as for ``proto:parse-schema-from-stream``.
181 The defaults for *name* and *class* are produced by taking the name of the
182 file and generating a name string and a class name symbol.
186 proto:parse-schema-from-stream (stream [Function]
187 &key name class conc-name)
189 Parses the contents of the stream *stream*, and returns the Protobufs
190 schema corresponding to the parsed file.
192 If *name* is supplied, it gives the Protobufs name (a string) for the
193 schema. If *class* is supplied, it gives the Lisp name (a symbol). These
194 are only used for display purposes.
196 *conc-name* is the default "conc name" to use for all of the messages
197 in the file. The default is "", which has the effect of giving eponymous
198 slot accessors to all of the classes generating during the import process.
202 proto:write-schema (schema &key stream type) [Function]
204 Pretty-prints the Protobufs schema *schema* onto the stream *stream*,
205 which defaults to ``*standard-output*``.
207 *type* can be either ``:proto`` or ``:lisp``.
210 CLOS classes to .proto conversion
211 ---------------------------------
213 If you have an existing set of CLOS classes that you would like to
214 convert to a Protobufs schema, you can use ``proto:generate-schema-from-classes``.
216 Note that the Protobufs schema is an *approximation* of a good schema.
217 You should review it and, if necessary, change it (and probably the Lisp
218 classes as well) until you have a good Protobufs schema definition.
222 proto:generate-schema-for-classes (classes [Function]
223 &key name package lisp-package
224 slot-filter type-filter enum-filter value-filter
225 alias-existing-classes)
227 Given a list of class names *classes*, this generates a Protobufs schema
228 for the classes, generating any necessary enum types that correspond to
229 Lisp ``member`` types. The return value is the model, rooted at an instance
230 of ``proto:protobuf-schema``.
232 *name* and *package* can be supplied to give the Protobufs name and
233 package. *lisp-package* can be supplied to give the name of the Lisp
234 package, if it is different from *package*. (Note that you should
235 still use ``in-package`` at the top of .lisp files, and it should
236 match the value of *lisp-package*.)
238 *slot-filter*, *type-filter*, *enum-filter* and *value-filter* are
239 filtering functions that can be used to weed out things from the Lisp
240 classes that should not be included in the Protobufs schema.
242 *slot-filter* is a function of two arguments, a list of all the slots
243 in the class and the slot currently being processed, and should return
244 true if the slot is to be kept or ``nil`` if it to be discarded. For
245 example, if there are internal implementation slots in a class that
246 need not appear in the Protobufs description, it can be used to filter
249 *type-filter* is a function of one argument, the type (of a slot); it
250 should return a "transformed" type if any is required. For example,
251 complex ``and`` and ``or`` types can't be directly represented in
252 Protobufs; this can be used to substitute something workable.
254 *enum-filter* is a function of one argument, a list of all the values
255 of a ``member`` type; it should return the transformed values. For
256 example, there maybe be some enumeration values that don't make sense;
257 they can be discarded by the filter.
259 *value-filter* is a function of one argument, the value of a slot
260 initform. It should transform the value into a scalar value suitable
263 If *alias-existing-classes* is true (the default), the generated
264 Lisp code will include ``:alias-for`` so that there will be no clash
265 with the existing Lisp class.
269 proto:write-schema-for-classes (classes [Function]
270 &key stream type name package lisp-package
271 slot-filter type-filter enum-filter value-filter
272 alias-existing-classes)
274 Given a list of class names *classes*, this generates a Protobufs schema
275 for the classes, generating enum types as necessary, and then
276 pretty-prints the result onto *stream*. *type* can be either ``:proto``
277 (the default) or ``:lisp``; it controls which format the generated
278 code will be printed in. The return value is the model, rooted at an
279 instance of ``proto:protobuf-schema``.
281 *name* and *package* can be supplied to give the Protobufs name and
282 package. *lisp-package* can be supplied to give the name of the Lisp
283 package, if it is different from *package*.
285 *slot-filter*, *type-filter*, *enum-filter* and *value-filter* are
286 as for ``proto:generate-schema-for-classes``.
288 *alias-existing-classes* is as for ``proto:generate-schema-for-classes``.
291 Using .proto files directly
292 ---------------------------
294 In addition to using the tools described above to convert between
295 .proto files and .lisp files, you can also use .proto files directly
296 in ASDF systems. Just use the ASDF module type ``:protobuf-file`` in
297 your system, and compile and load the system in the usual way. This
298 will create both the Protobufs model and the Lisp classes that
299 correspond to the Protobufs messages. (Note that it will also leave a
300 .lisp file having the same name as the .proto file in the file
304 A note on Lisp packages
305 ~~~~~~~~~~~~~~~~~~~~~~~
307 When using an existing .proto file directly, it will likely contain a
308 ``package`` line, but not a ``lisp_package`` line. CL-Protobufs needs
309 to choose some package to use. Here is what it does:
311 - The package name from the ``package`` line is converted to a more
312 Lisp-like name, e.g., ``fortune_teller`` becomes ``fortune-teller``.
313 - If the Lisp package exists (i.e., you have previously used
314 ``defpackage`` to define the packaged), then CL-Protobufs just
316 - If the Lisp package does not exist, CL-Protobufs creates a new
317 package of the given name that uses no other packages, not even
318 the ``common-lisp`` package. In addition, the symbols naming all
319 of the enum types, message types, field name and service method
320 names are exported from the new package.
323 Using the Protobufs macros
324 --------------------------
326 You can define a Protobufs schema entirely within Lisp by using the
327 following macros. For example::
329 (proto:define-schema color-wheel
330 (:package com.google.colorwheel
331 :lisp-package color-wheel)
332 (proto:define-message color-wheel
333 (:conc-name color-wheel-)
335 (colors :type (proto:list-of color) :default ()))
336 (proto:define-message color
338 (name :type (or string null))
339 (r-value :type integer)
340 (g-value :type integer)
341 (b-value :type integer)
342 (proto:define-extension 1000 max))
343 (proto:define-extend color ()
344 ((opacity 1000) :type (or null integer)))
345 (proto:define-message get-color-request ()
346 (wheel :type color-wheel)
348 (proto:define-message add-color-request ()
349 (wheel :type color-wheel)
351 (proto:define-service color-wheel ()
352 (get-color (get-color-request color)
353 :options (:deadline 1.0))
354 (add-color (add-color-request color)
355 :options (:deadline 1.0))))
357 This will create the Protobufs model objects, Lisp classes and enum
358 types that correspond to the model. The .proto file of the same schema
359 looks something like this::
363 package com.google.colorwheel;
365 option (lisp_package) = "color-wheel";
368 required string name = 1;
369 repeated Color colors = 2;
373 optional string name = 1;
374 required int64 rValue = 2;
375 required int64 gValue = 3;
376 required int64 bValue = 4;
377 extensions 1000 to max;
381 optional int64 opacity = 1000;
384 message GetColorRequest {
385 required ColorWheel wheel = 1;
386 required string name = 2;
389 message AddColorRequest {
390 required ColorWheel wheel = 1;
391 required Color color = 2;
395 rpc GetColor (GetColorRequest) returns (Color) {
396 option deadline = 1.0;
398 rpc AddColor (AddColorRequest) returns (Color) {
399 option deadline = 1.0;
403 Note that Lisp types ``(or null <T>)`` turn into optional fields,
404 and Lisp types ``(proto:list-of <T>)`` and ``(proto:vector-of <T>)``
405 turn into repeated fields representing by lists or vectors,
408 Note also that the macros have assigned indexes to the fields for each
409 method; similarly, they will assign values to enumerations as well.
410 *This is not stable*, that is, if you add new fields or enum values,
411 the indexes could change, which would result in an incompatible
416 proto:define-schema (type (&key name syntax import [Macro]
418 optimize options documentation)
421 Defines a Protobufs "schema" whose name is given by the symbol *type*,
422 corresponding to a .proto file of that name. By a "schema", we mean an
423 object that corresponds to the contents of one .proto file. If *name*
424 is not supplied, the Protobufs name of the schema is the camel-cased
425 rendition of *type* (e.g., the schema named ``color-wheel``, by
426 default, becomes ``ColorWheel``); otherwise the Protobufs name is the
429 *imports* is a list of pathname strings to be imported. This corresponds
430 to ``import`` in a .proto file. Note that ``proto:define-schema`` can
431 import both .proto files and .lisp files containing Protobufs macros,
432 but the generated .proto code will convert all of these to imports of
435 *syntax* and *package* are strings that give the Protobufs syntax and
436 package name. *lisp-package* can be supplied to give the name of the
437 Lisp package, if it is different from *package*. *package* corresponds
438 to ``package`` in a .proto file. If you want to specify a Lisp package
439 in a .proto file, you can use ``option (lisp_package)``.
441 *optimize* can be either ``:space`` (the default) or ``:speed``. When it
442 is ``:space`` the serialization methods generated for each message are
443 compact, but slower; when it is ``:speed``, the serialization methods
444 will be much faster, but will take more space. This corresponds to
445 ``option optimize_for = CODE_SIZE|SPEED`` in a .proto file.
447 *options* is a property list whose keys and values are both strings,
448 for example, ``:option ("java_package" "com.yoyodyne.overthruster")``.
449 They are passed along unchanged to the generated .proto file.
451 *documentation* is a documentation string that is preserved as a comment
454 *body* consists of any number of calls to ``proto:define-enum``,
455 ``proto:define-message``, ``proto:define-extend`` or ``proto:define-service``.
459 proto:define-enum (type (&key name conc-name alias-for [Macro]
460 options documentation)
463 Defines a Protobufs enum type and a corresponding Lisp deftype whose name
464 is given by the symbol *type*. If *name* is not supplied, the Protobufs
465 name of the enum is the camel-cased rendition of *type*; otherwise the
466 Protobufs name is the string *name*. If *conc-name* is given, it will
467 be used as the prefix for all of the enum value names. In a .proto file,
468 you can use ``option (lisp_name)`` to override the default name for the
471 If *alias-for* is given, no Lisp deftype is defined. Instead, the enum
472 will be used as an alias for a ``member`` type that already exists in Lisp.
473 You can use ``option (lisp_alias)`` in a .proto file to give the Lisp
474 alias for an enum type.
476 *options* is a property list whose keys and values are both strings.
478 *documentation* is a documentation string that is preserved as a comment
481 *body* consists of the enum values, each of which is either a symbol
482 or a list either of the form ``(name index)`` or ``(name &key index)``.
483 By default, and if you have not explicitly given an index, the indexes
484 start at 0 and are incremented by 1 for each new enum value. For
485 schema forward and backward compatibility, you should always use the
486 explicit form, either ``(name index)`` or ``(name &key index)``.
488 ``proto:define-enum`` can be used only within ``proto:define-schema``
489 or ``proto:define-message``.
493 proto:define-message (type (&key name conc-name alias-for [Macro]
494 options documentation)
497 Defines a Protobuf message and a corresponding Lisp defclass whose
498 name is given by the symbol *type*. If *name* is not supplied, the
499 Protobufs name of the class is the camel-cased rendition of *type*
500 (e.g., the class named ``color-wheel``, by default, becomes
501 ``ColorWheel``); otherwise the Protobufs name is the string *name*. If
502 *conc-name* is given, it will be used as the prefix for all of the
503 slot accessor names. In a .proto file, you can use ``option (lisp_name)``
504 to override the default name for the class in Lisp.
506 If *alias-for* is given, no Lisp defclass is defined. Instead, the
507 message will be used as an alias for a class that already exists in
508 Lisp. This feature is intended to be used to define messages that will
509 be serialized from existing Lisp classes; unless you get the slot names,
510 readers and writers exactly right for each field, it will be the case
511 that trying to (de)serialize into a(n aliased) Lisp object won't work.
512 You can use ``option (lisp_alias)`` in a .proto file to give the Lisp
513 alias for the class corresponding to a message.
515 *options* is a property list whose keys and values are both strings.
517 *documentation* is a documentation string that is preserved as a comment
520 The body *fields* consists of fields, ``proto:define-enum``,
521 ``proto:define-message`` or ``proto:define-extension`` forms.
523 Fields take the form ``(slot &key index type name default reader writer)``.
524 *slot* can be either a symbol giving the slot name or a list of the
525 form ``(slot index)``. By default, the field indexes start at 1 and
526 are incremented by 1 for each new field value. *type* is the type of
527 the slot. For schema forward and backward compatibility, you should
528 always use either the ``(slot index)`` form or supply ``:index``.
530 *name* can be used to override the defaultly generated Protobufs field
531 name (for example, a Lisp field called ``color-name``, by default,
532 becomes ``color_name``). *default* is the default value for the
533 slot. *reader* is the name of a Lisp slot reader function to use to
534 get the value during serialization, as opposed to using
535 ``slot-value``; this is meant to be used when aliasing an existing
536 class. *writer* can be similarly used to name a Lisp slot writer
539 Note that the Protobufs does not support full Lisp type expressions in
540 the types of fields. The following type expressions are supported:
542 - ``integer``, optionally with upper and lower bounds
543 - ``signed-byte``, which correspond to ``proto:int32`` or ``proto:int64``
544 - ``unsigned-byte``, which correspond to ``proto:uint32`` or ``proto:uint64``
545 - ``float`` and ``double-float``
546 - ``string``and ``character``
547 - ``(array (unsigned-byte 8))``, which corresponds to ``proto:byte-vector``
549 - ``(member ...)``, where all the members are symbols or keywords or ``nil``
550 - the name of a class that corresponds to another Protobufs message
551 - ``(proto:list-of <T>)``, where ``<T>`` is any of the above types
552 - ``(proto:vector-of <T>)``, where ``<T>`` is any of the above types
553 - ``(or <T> null)``, where ``<T>`` is any of the above types
555 ``member`` corresponds to a Protobufs ``enum``. ``(or <T> null)``
556 corresponds to an optional field. ``proto:list-of`` corresponds to a
557 repeated field, and the Lisp slot will be typed as a list. ``proto:vector-of``
558 corresponds to a repeated field, and the Lisp slot will be typed as an
559 adjustable array with a fill pointer. The other types correspond to
560 the various Protobufs scalar field types.
562 ``proto:define-message`` can be used only within ``proto:define-schema``
563 or ``proto:define-message``.
567 proto:define-extension (from to) [Macro]
569 Defines a field extension for the indexes from *from* to *to*.
570 *from* and *to* are positive integers ranging from 1 to 2^29 - 1.
571 *to* can also be the token ``max``, i.e., 2^29 - 1.
573 Once an extension to a message has been defined, you can use
574 ``proto:define-extends`` to add new fields.
576 ``proto:define-extension`` can be used only within ``proto:define-message``.
578 In non-Lisp implementations of Protobufs, you set and get the value
579 of an extension using functions like ``SetExtension()`` and
580 ``GetExtension()``. For example, if you extended a ``Color`` message
581 to have an ``opacity`` field, you would set the field using something
585 color.SetExtension(opacity, 0.5);
587 In Common Lisp Protobufs, you can just use an ordinary slot accessor::
589 (let ((color (make-instance 'color)))
590 (setf (color-opacity color) 0.5))
594 proto:define-extend (type (&key name conc-name [Macro]
595 options documentation)
598 Defines a Protobuf ``extend``, that is, an extension to an existing
599 message (and corresponding Lisp class) that has additional fields that
600 were reserved by ``proto:define-extension``. *type* and *name* are as
601 for ``proto:define-message``. Note that no new Lisp class is defined;
602 the additional slots are implemented as getter and setter methods on
603 a closed-over variable. The other options, such as *conc-name* and
604 *alias-for* are take from the extended message.
606 *options* is a property list whose keys and values are both strings.
608 *documentation* is a documentation string that is preserved as a comment
611 The body *fields* consists only of fields, which take the same form as
612 they do for ``proto:define-message``.
614 ``proto:define-extend`` can be used only within ``proto:define-schema``
615 or ``proto:define-message``.
619 proto:define-service (type (&key name [Macro]
620 options documentation)
623 Defines a Protobufs service named *type* and corresponding Lisp generic
624 functions for all its methods. If *name* is not supplied, the Protobufs
625 name of the service is the camel-cased rendition of *type*; otherwise
626 the Protobufs name is the string *name*.
628 *options* is a property list whose keys and values are both strings.
630 *documentation* is a documentation string that is preserved as a comment
633 The body is a set of method specs of the form
634 ``(name (input-type [=>] output-type &key streams) &key options documentation)``.
636 For each method spec, *name* is a symbol naming the RPC method.
637 *input-type* and *output-type* give the input and output types of the method;
638 they may either be symbols or a list of the form ``(type &key name)``.
639 You can optionally include the symbol ``=>`` between the input and
640 output types; this seems to improve readability.
642 *streams* is also the name of a type, and provides a hook to RPC
643 implementations that implement "streaming".
645 ``proto:define-service`` can only be used within ``proto:define-schema``.
651 The following types are defined in the ``protobufs`` package:
653 - ``proto:int32``, which corresponds to the Protobufs ``int32`` type
654 - ``proto:int64``, which corresponds to the Protobufs ``int64`` type
655 - ``proto:uint32``, which corresponds to the Protobufs ``uint32`` type
656 - ``proto:uint64``, which corresponds to the Protobufs ``uint64`` type
657 - ``proto:sint32``, which corresponds to the Protobufs ``sint32`` type
658 - ``proto:sint64``, which corresponds to the Protobufs ``sint64`` type
659 - ``proto:fixed32``, which corresponds to the Protobufs ``fixed32`` type
660 - ``proto:fixed64``, which corresponds to the Protobufs ``fixed64`` type
661 - ``proto:sfixed32``, which corresponds to the Protobufs ``sfixed32`` type
662 - ``proto:sfixed64``, which corresponds to the Protobufs ``sfixed32`` type
663 - ``proto:byte-vector``, which corresponds to the Protobufs ``bytes`` type
664 - ``proto:list-of``, which corresponds to a repeated field
665 - ``proto:vector-of``, which corresponds to a repeated field
667 The following existing Lisp type correspond to other Protobufs types:
669 - ``string`` is the Protobufs UTF-8 encoded ``string`` type
670 - ``boolean`` is the Protobufs ``bool`` type
671 - ``float`` is the Protobufs ``float`` type
672 - ``double-float`` is the Protobufs ``double`` type
673 - ``member`` of a set of keywords generates a Protobufs ``enum`` type
675 Note that ``(or <T> null)`` corresponds to an optional field.
678 Protobufs service stubs
679 ~~~~~~~~~~~~~~~~~~~~~~~
681 When you use the ``proto:define-service`` macro to define a service
682 with some methods, the macro defines "stubs" (CLOS generic functions)
683 for each of the methods in the service. Each method named ``foo`` gets
684 a client stub and a server stub whose signatures are, respectively::
686 foo (rpc-channel request &key callback) => response
687 do-foo (rpc-channel request) => response
689 The type of *rpc-channel* is unspecified, but is meant to be a
690 "channel" over which the RPC call will be done. The types of *request*
691 and *response* are message classes that were defined via
692 Protobufs. *callback* is a function of two arguments, the RPC channel
693 and the response; it is intended for use by asynchronous RPC calls.
695 For example, this fragment defines four stubs::
697 (proto:define-service color-wheel ()
698 (get-color (get-color-request color))
699 (add-color (add-color-request color)))
701 The client stubs are ``get-color`` and ``add-color``, the server stubs
702 are ``do-get-color`` and ``do-add-color``. An RPC library will implement
703 a method for the client stub. You must fill in the server stub yourself;
704 it will implement the desired functionality.
706 The client stub also gets a single method defined for it that looks like
707 something like this::
709 (defmethod foo (rpc-channel (request input-type) &key callback)
710 (let ((call (and *rpc-package* *rpc-call-function*)))
711 (funcall call rpc-channel method request :callback callback)))
713 where *rpc-channel*, *request* and *callback* are as above.
714 The special variables ``*rpc-package*`` and ``*rpc-call-function*``
715 are filled in when the RPC package is loaded. *method* is the
716 ``proto:protobuf-method`` that describes the method; this is
717 included so that the RPC implementation can determine what type
718 of response object to create, what timeout to use, etc.
720 It is beyond the scope of this Protobufs library to provide the RPC
721 service; that is the domain of another library.
724 Serializing and deserializing
725 =============================
727 You can serialize from Lisp objects or deserialize into Lisp objects
728 using either the fast and compact Protobufs wire format, or the
729 human-readable text format.
737 proto:serialize-object-to-stream (object type [Function]
740 Serializes the object *object* of type *type* onto the stream *stream*
741 using the wire format. *type* is the Lisp name of a Protobufs message
742 (often the name of a Lisp class) or a ``proto:protobuf-message`` object.
743 *type* defaults to the class of *object*
745 The element type of *stream* must be ``(unsigned-byte 8)``.
747 *visited* is an ``eql`` hash table used to cache object sizes. If it is
748 supplied, it will be cleared before it is used; otherwise, a fresh table
751 The returned value is a byte vector containing the serialized object.
752 If the stream is ``nil``, the buffer is not actually written anywhere.
756 proto:serialize-object (object type buffer [Generic function]
757 &optional start visited)
759 Serializes the object *object* of type *type* into the byte array
760 *buffer* using the wire format. *type* is the Lisp name of a Protobufs
761 message (often the name of a Lisp class) or a ``proto:protobuf-message``
762 object. *type* defaults to the class of *object*. The buffer is assumed
763 to be large enough to hold the serialized object; if it is not, an
764 out-of-bounds condition may be signaled.
766 The object is serialized using the wire format into the byte array
767 (i.e., a vector whose type is ``(unsigned-byte 8)``) given by *buffer*,
768 starting at the fixnum index *start* .
770 *visited* is an ``eql`` hash table used to cache object sizes.
772 The returned values are the modified buffer containing the serialized
773 object and the index that points one past the last serialized byte in
774 the buffer, which will be the number of bytes required to serialize the
775 object if *start* was 0.
777 Note that ``proto:serialize-object`` will not correctly serialize a
778 set of objects that has cycles. You must resolve these yourself.
782 proto:deserialize-object-from-stream (type &key stream) [Function]
784 Deserializes an object of the given type *type* as a Protobuf object.
785 *type* is the Lisp name of a Protobufs message (usually the name of a
786 Lisp class) or a ``proto:protobuf-message``.
788 The element type of *stream* must be ``(unsigned-byte 8)``.
790 The returned value is the deserialized object.
794 proto:deserialize-object (type buffer &optional start end) [Generic function]
796 Deserializes an object of the given type *type* as a Protobufs object.
797 *type* is the Lisp name of a Protobufs message (usually the name of a
798 Lisp class) or a ``proto:protobuf-message``.
800 The encoded bytes come from the byte array given by *buffer*, starting
801 at the fixnum index *start* up to the end of the buffer, given by *end*.
802 *start* defaults to 0, *end*' defaults to the length of the buffer.
804 If a zero byte is encountered in in the "tag position" during
805 deserialization, this is interpreted as an "end of object" marker
806 and deserialization stops.
808 The returned values are the deserialized object and the index into the
809 buffer at which the deserialization ended.
813 proto:object-size (object type &optional visited) [Generic function]
815 Computes the size in bytes of the object *object* of type *type*.
816 *type* is the Lisp name of a Protobufs message (usually the name of a
817 Lisp class) or a ``proto:protobuf-message``. *type* defaults to the
820 *visited* is an ``eql`` hash table used to cache object sizes.
822 The returned value is the size of the serialized object in bytes.
830 proto:print-text-format (object &optional type [Function]
831 &key stream suppress-line-breaks)
833 Prints the object *object* of type *type* onto the stream *stream* using
834 the textual format. *type* defaults to the class of *object*.
836 If *suppress-line-breaks* is true, all the output is put on a single line.
840 proto:parse-text-format (type &key stream) [Function]
842 Parses the textual format of an object of the given type *type*. *type*
843 is the Lisp name of a Protobufs message (usually the name of a Lisp
844 class) or a ``proto:protobuf-message``. The input is read from the
847 The returned value is the object.
858 proto:get-extension (object slot) [Generic function]
860 Returns the value of the extended slot *slot* in the object *object*.
862 Since you can just use the ordinary slot reader function, you should
863 not need to call ``proto:get-extension``. It is included for compatibility
864 with other Protobufs APIs.
868 proto:set-extension (object slot value) [Generic function]
870 Sets the value of the extended slot *slot* in the object *object*
873 Since you can just use the ordinary slot writer function, you should
874 not need to call ``proto:set-extension``. It is included for compatibility
875 with other Protobufs APIs.
879 proto:has-extension (object slot) [Generic function]
881 Returns true iff the object *object* has any value for the extended
886 proto:clear-extension (object slot) [Generic function]
888 Removes the value for the extended slot *slot* in the object *object*.
891 Initialization functions
892 ------------------------
896 proto:object-initialized-p (object type) [Generic function]
898 Returns true iff all of the fields of *object* of type *type* are
899 initialized, i.e., there are no fields whose value is unbound.
903 proto:slot-initialized-p (object type slot) [Generic function]
905 Returns true iff the field *slot* of *object* of type *type* is
906 initialized, i.e., there are no fields whose value is unbound.
910 proto:reinitialize-object (object type) [Generic function]
912 Initializes all of the fields of *object* of type *type* to their
916 Python compatibility functions
917 ------------------------------
919 By popular demand, the Protobufs library provides an API that is very
920 similar to the API of the Python Protobufs library.
924 proto:is-initialized (object) [Generic function]
926 Returns true iff all of the fields of *object* are initialized, i.e.,
927 there are no fields whose value is unbound.
931 proto:has-field (object slot) [Generic function]
933 Returns true iff the field *slot* is initialized in *object*.
937 proto:clear (object) [Generic function]
939 Initializes all of the fields of *object* to their default values.
943 proto:serialize (object &optional buffer start end) [Generic function]
945 Serializes *object* into *buffer* using the wire format, starting at the
946 index *start* and going no further than *end*. *object* is an object
947 whose Lisp class corresponds to a Protobufs message.
951 proto:merge-from-array (object buffer &optional start end) [Generic function]
953 Deserializes the object encoded in *buffer* into *object*, starting at
954 the index *start* and ending at *end*. *object* is an object whose Lisp
955 class corresponds to a Protobufs message.
959 proto:octet-size (object) [Generic function]
961 Returns the number of bytes required to serialize *object* using the
962 wire format. *object* is an object whose Lisp class corresponds to a
969 CL-Protobufs includes some Lisp-only extensions that have no
970 counterpart in Protobufs, but which "ground out" to compatible
979 proto:define-type-alias (type (&key name alias-for [Macro]
981 &key lisp-type proto-type
982 serializer deserializer)
984 Defines a Lisp type alias named *type* whose Lisp type is *lisp-type*
985 and whose Protobufs type is *proto-type*. *lisp-type* must be a valid
986 Lisp type expression; *proto-type* myst be a Protobufs primitive type
987 (e.g., ``int32``, ``string``).
989 *serializer* is a function of one argument that takes an object of
990 type *lisp-type* and returns an object having the Protobufs primitive
991 type *proto-type*. *deserializer* is a function of one argument that
992 takes an object of type *proto-type* and returns an object having the
995 If *name* is not supplied, the Protobufs name of the type alias is the
996 camel-cased rendition of *type*; otherwise the Protobufs name is the
999 If *alias-for* is given, no Lisp deftype for ``type`` is
1000 defined. Instead, the type alias is assumed to refer to a
1001 previously-defined Lisp type.
1003 For example, this Lisp schema::
1005 (proto:define-schema revision-history
1006 (:package revision-history)
1007 (proto:define-type-alias date ()
1010 :serializer integer-to-date
1011 :deserializer date-to-integer)
1012 (proto:define-message revision ()
1013 (proto:define-message metadata ()
1014 (author :type (or null string))
1015 (revision :type (or null string))
1016 (date :type (or null date)))
1018 (description :type string)))
1020 will generate this Protobufs schema::
1024 optional string author = 1;
1025 optional string revision = 2;
1026 // alias maps Lisp integer to Protobufs string
1027 optional string date = 3;
1029 required string name = 1;
1030 required string description = 2;