Well in general my understanding is that Xindice was designed to handle a lot of small files, not large files. Thus, even if Xindice was able to handle binary files, you might still run into issues with the size of your files. You might look into a chunking approach.
-Matt > -----Original Message----- > From: Fernando Padilla [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 26, 2002 3:32 PM > To: [EMAIL PROTECTED] > Subject: RE: Binary Files > > On Wed, 26 Jun 2002, Matt Liotta wrote: > > > I don't think it would be that hard to implement the BinaryResource > > interface. Nor do I think anyone would mind having that be part of > > Xindice. I would imagine the only reason it was implemented is that none > > of us find it particularly interesting. With that being said there is a > > relatively easy work around. Simply Base64 encode the binary file and > > embed it as CData in an XML document. In fact, this could be the crude > > implementation of BinaryResource until someone wants to do a better job. > > > > -Matt > > > I know that's what we finally settled on, right before I asked about > proper BinaryResource support. But I might as well ask some questions I > have about that. Done Xindice have limitations on the node sizes? > > like, a 1MB file would get converted into a 2M character string. That's a > huge node to load into memory, aside from a huge string for java to deal > with. I'm also afraid that that 2M char string is actually 4M (2byte > chars) in memory, so you see how files could easily take over the memory > of the system having it grind to a halt... > > Anybody have thoughts on this? > > ps - this is just academic meanderings, because really BinaryResource > should be implemented...
