| |
| | recursive types, struct, custom, dict, etc. |
 | | We have type CUSTOM which is: typecode = CUSTOM, name of type, array of bytes where array of bytes is an unknown opaque blob interpreted by the message recipient based on "name of type" only if the recipient has existing knowledge of how to interpret blobs with this type name. |
 | | For the type signature format, right now "array of array of string" is "aas" and "int" is "i" and so forth; so e.g. |
 | | Struct names: I think there's a good argument to be made that struct names should not be in the type signature or protocol, but instead be in the introspection data (where we also have arg names already, and could add struct field names in addition to the name of the struct itself). |
| lists.freedesktop.org /pipermail/dbus/2004-June/001169.html (1018 words) |
|