Re: Binary and XML serialization of types

[hanslad@gmail.com]

> 
> In the case 2, you should consider using packets instead of a raw octet
> 
> stream. Typically you would form an outgoing packet in the memory, using
> 
> whatever means (e.g. by a string-mapped stream) and then send the packet
> 
> out as a whole. It is especially important to do if you are going to use
> 
> NO_DELAY socket option.
> 
> 

This sounds interesting. Do you know any good examples of this? 

 
> 
> Is it a custom protocol you are going to invent? Anyway, the protocols
> 
> usually deploy some sort of packet header to describe the request and the
> 
> body of. The most efficient way is when the body length can be determined
> 
> from the header. You read the body into memory and then parse it, e.g.
> 
> using a string-mapped stream.
> 

The protocol is certanly not invented by me(OPC UA), but I want to implement it in Ada as a long term hobby project. The base types(int, IEEE-754 float) is encoded with the least significant byte appearing first (i.e. little endian).
 
> 
> > For me it would be locical to separate all the "wire information" from the
> 
> > type information. Today, the binary and xml encoding scheme is defined,
> 
> > and I had hope to be able to separate this in different packages.
> 
> 
> 
> That is doable.
> 

A simple example would be great!
As a total Ada beginner, any code examples or references to it will help me alot.

Thanks

HP