dev@fi.java.net

Re: setFeature Bug?

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Wed, 04 Jan 2006 10:01:10 +0100

Alan Hudson wrote:
> Paul Sandoz wrote:
>
>> Hi Alan,
>>
>> Yes, this is a bug, thanks for finding this.
>>
>> I have just fixed this (and included some simple unit tests). An
>> automated build should be pushed to java.net soon, hopefully by the
>> time you read this.
>>
>> Paul.
>>
> thank you.
>
> What is the next public release cycle for FI?

We have nothing planned in the immediate time-frame. FI tends to be
"under the covers" and utilized by our JAXB and JAX-RPC 1.x and JAX-WS
2.0 versions, and these are, or are becoming, stable so we do not want
to destabalise things in this respect.

With respect to what we have planned, the next changes would be in
relation to better performant integration into JAXB 2.x and JAX-WS 2.x
e.g. currently we do not take advantage of all the encoding algorithms
for use with JAXB (only the base64 encoding algorithm). To do this
properly will require some augmentations to the StAX API and therefore
the FI StAX implementation. Things are just getting started... if all
things go well then something stable and public is likely to be ready in
about 6 months.

You can also help/decide here with respect to what you would like in the
next release and when, and i would be happy to co-ordinate another
stable/public release based on that.


> I'll be working a fair
> bit on X3D binary the coming month or two, so I expect I'll have some
> code to give back to the project.

That would be great.


> I'd definately like to look at the
> bucket gzip code again.

Great, me to, with your help :-)


> On another project I solved how to use Sun's
> zip code instead of going to the another library. Still cop a 16 bit
> change cost so I'm not sure whether it will be as effecient as a global
> gzip.
>

Probably not. I guess it depends on the size of chunks that are being
compressed. If we had this fragment:

<a id="_option_1"/>
<a id="_option_2"/>
<a id="_option_3"/>
<a id="_option_4"/>
<a id="_option_5"/>

and wanted to compression all 'id' attributes using a stream-zip
encoding algorithm, then what would be the size of the compressed chunk
compared to the size of encoding the literal information?

Paul.

-- 
| ? + ? = To question
----------------\
    Paul Sandoz
         x38109
+33-4-76188109