Hello

> Using the Java3D compression mechanism (objtocg) works VERY well as the
> files get down to around 400K to 600K, but the CompressedGeometryFile was
> not written to allow the use of URLs.

Why do you use CompressedGeometryFile at all ?

Create the compressed data as usual. On the client-side use
CompressedGeometry(CompressedGeometryHeader hdr, byte[] compressedGeometry)
to get your data back (CompressedGeometry.decompress(), anyone ?)

> Note that I have tried to create a RandomAccessFile as a temporary File on
> the applet side (using a signed applet) to receive the InputStream from my
> servlet, but the results were slower than sending the uncompressed images
> (much slower in fact).

Uncompressing is not for free. The algo is slow, even with normal
non-temp-files.

cu

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to