Re: to be effcient or not to be efficient

Attila Kinali wrote:

>>Of course it depends if you prefer compatibility more (or less) than 
>>speed. But as a communication means, it's more general. Then internaly 
>>you are free to use structs directly. You just then have to convert the 
>>data between the struct and the "EBML" data when you need communication.
> 
> 
> The problem is, that you may not add the video data into the ebml messages
> or you will just waste a lot of time packaging and unpackaging it.
> But then, where is the sense of having such a system ?

Now that's a good point. So you can add "pointer" to the list of types 
for IDs.

As I said, it's not pure EBML, just simplified. It's basic TLV.

But the packing/unpacking thing is for sure a speed issue... That 
depends on where you draw the line of extensibility and speed.