As I understand it, the new XML-RPC will replace the CORBA interface. However, from the Xindice Users point of view, our interface, the XML:DB API won't change. It should mean that our client code shouldn't have to change.
But that means that there is a network layer between the data. It sounds like, if we want an XML:DB API without any CORBA or XML-RPC, we will have to write it ourselves. Or since this is an open source, we can write one and submit it as part of the project :-). However, we lose the command-line tools. Which for some people that is a good thing. It is a bit of a security hazard. However, if we use the CORBA/XML-RPC which has a security hazard, we also get third-party access and third-party tools. I will have to think about whether or not I need to bypass|re-implement the XML:DB API. Does anyone else need this bad enough to sit down and write the code? Mark Matt Liotta wrote: > > As long as you don't need the command line tools, embedding without > all > > the CORBA mess seems like it has good potential. It will also remove > any > > security concerns tied directly to the database, your app will be in > > control of all security. If you're planning two versions you'd > definitely > > want to implement a local version of the XML:DB API to make changing > your > > code simpler. It's really not that hard of a thing to do. > > > If I read this correctly, you are saying the XML:DB API is implemented > by CORBA specific classes. That doesn't seem to make sense. Wouldn't it > make more sense to have an implementation of XML:DB that isn't tied to > CORBA and then layer CORBA on top of that? I would certainly rather use > an implementation that isn't tied to CORBA. > > -Matt -- Mark J Stang 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
