Paul Sandoz wrote:
> Alan Hudson wrote:
>
>>> Yes, we have reserved space for additional built-in encoding
>>> algorithms.
>>>
>> ok. I'm going to prototype the BYTE one(pretty easy from the
>> SHORT/INT code). And I'll report back on how it affects X3D
>> compression/parsing rates.
>>
>
> OK, so this will have to be an application defined encoding algorithm.
>
> I think the support for application defined algorithms probably needs
> some tweaking for more optimized encoding and decoding. This could be
> a good use case to test.
>
will do.
I'm trying to remember the spec details. By having it be an app-defined
algo it will be slightly larger right? Ie isn't there a small size
savings encodings as default?