Correct me if I am wrong, but isn't a Resource atomic? Except for queries, all of my code treats Resources as something associated with a key. If that is the case with BinaryResources, shouldn't they be treated like BLOBs? In which case, couldn't we just store them as individual files and in the collection annotate it as such? What am I missing?
Mark Fernando Padilla wrote: > 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... -- Mark J Stang System Architect Cybershop Systems
begin:vcard n:Stang;Mark x-mozilla-html:TRUE adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Mark Stang end:vcard
