It was actually an explicit decision not to expose this. It was one of those things where you have to ask is it really necessary? At the time the conclusion was no it wasn't. What are the major use cases where this is necessary? What is the value add over using the file system? If we have good answers here then we certainly could expose the binary functionality.
The XML:DB API does already have a BinaryResource concept, we just don't implement it.


On Friday, June 21, 2002, at 01:36  PM, Fernando Padilla wrote:


Interesting. So no one has bothered to expose this, i think vital piece of functionality?? :) Well, at least now we know it's possible without totatly reengineering Xindice... maybe I'll take a look at the code to expose it at xmldb collections.. It wouldn't break the services that expect XMLResources right? like XPath, XUpdate, etc??

fernando



On Fri, 21 Jun 2002, Tom Bradford wrote:

On Friday, June 21, 2002, at 09:23 AM, Fernando Padilla wrote:
I am wondering about support for Binary files.. Any ideas? plans?

The very first versions of dbXML-Core supported binary storage, and the internal APIs still do it if you bypass the XML system:

Collection.getFiler().readRecord(...)
Collection.getFiler().writeRecord(...)

It's just that none of this stuff is exposed by the client server APIs.

--
Tom Bradford - http://www.tbradford.org
Architect - XQRL (XQuery Engine) - http://www.xqrl.com
Apache Xindice (XML Database) - http://xml.apache.org/xindice
Labrador (Web Services Hub) - http://www.notdotnet.org/labrador




Kimbro Staken
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org



Reply via email to