Better documentation will be forthcoming, but the library needs to settle first. For now I recommend skipping libobjects.info and reading the header files instead. The overview of classes below should help you see the big picture as you read the source. Here is the class inheritance heirarchy. Stream objects provide a consistent interface for reading and writing bytes.
Coders provide a formatted way of writing to Streams.
Coders and streams can be mixed and matched so that programmers can choose the destination and the format separately. Neither the stream or coder class heirarchies are very mature yet. I threw them together because I needed them for distributed objects. This version of the distributed objects only works with sockets. A Mach port back-end should be on the way.