-
-
2. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
> "JAI Image I/O Tools provides reader, writer, and
> stream plug-ins for the Java Image I/O Framework..."
> That means we could add a lot more image formats to
> JBoss Media!
Sounds great, but
>"...The supplied streams and
> associated service providers use the New I/O APIs."
Do we need to make such things optional to retain 1.3.x support? -
3. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
As far as I know we realy have to be compiliant with 1.3 . Problem here is that we are mapping too much unknown territory and media is just coming to java.
The way I am thinking about it at the moment is to have a generic 1.3 compiliant version and other and a bunch of other versions with support for the specific platform/ system.
Another option is to have the system qeury/autodetect in which platform we are and load the correct libraries.
SpSa -
4. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
How about we get the framework working in 1.3, then review and have a look at what bits 1.4 may improve and how best to fit them in?
-
5. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
I don't think Enterprise Media Beans are going to be included in J2EE 1.4, which has a J2SE 1.4 requirement (am I right on this or not?)..
But using the new Image I/O APIs available in J2SE 1.4 is the way to go, IMHO. At least for image support in EMB.
If we want to support J2SE 1.3 *maybe* what we need to do is re-implement the JSR 15 (Image I/O Framework Specification).
Since JBoss Media should have pluggable codecs, maybe that excercise should be left for someone else. Using the new Image I/O makes the implementation a lot easier, at least for now.
Ricardo -
6. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
I guess individual codecs using 1.4 APIs isn't so much of a problem - I was thinking more about keeping 1.4 code out of any of the infrastructure code.
-
7. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
I agree that having individual codecs requiring 1.4 isn't such a bad thing, but I think that the core of the framework (i.e. the stuff that needs to be there all the time) should just use 1.3.
Make sense? -
8. Re: Java Advanced Imaging Image I/O Tools 1.0-RC is now avai
The core framework doesn't use 1.4 APIs, but I was thinking about including the 1.4's java.nio.* APIs to increase performance.
I believe we should deliver the simplest and better implementation of the spec... if we must use new APIs to complish that, we have no other choice than use them, and worry about 1.3 compatibility latter.
What do you all think?
Ricardo
