Serialization

A Message's Address and its data needs to be serialised to be past over the connection.

The serialization mechanism should be configurable negociatable per connection. This would allow IKC to be extented to other languages.

Some data can't be serialized, such as coderefs, filehandles, etc. IKC2 could have some marshalling mechanism that prepares the parameters before they are serialized.

One example of marshalling is with a coderef. It could be saved on it's native kernel. The foreign kernel then gets a coderef that sends a message back to the native kernel. This would require a re-entrant POE kernel if the foreign kernel then requires the coderef's return value.