Staken-san wrote:
> I'd like to hear thoughts on moving Xindice to run under a servlet engine.
> [...]
>
> The main downside is that things like the CORBA API hang off the old
> server framework and wouldn't be able to work anymore.
I've been lurking for quite a while. I think it's great that you've been
working hard at cleaning everything up recently. Nonetheless, let's step
back and look at what is happening.
1. The basic Xindice server will be a stand-alone (embedded) version
with a set of interfaces to access and manipulate data.
2. Add-on protocols (which fire up factories) may be implemented to
handle accessing data remotely - allowing for RMI, SOAP, CORBA,
and other RPC-type binding mechanisms.
Please correct me if any of this is wrong.
If the above is accurate, I can see several possible servlet container uses:
1. A class that exposes the interface and runs embedded as an Apache Axis
web service (Xindice is in the same VM as the application server).
2. A class that exposes the interface and has some additional configura-
tion parameters to specify where to locate Xindice (protocol, server,
etc.)
3. A custom application that uses it, either embedded or with one of
the add-on protocols.
You said in a previous message that you wanted to be able to focus on the main
database engine, not all of this connectivity stuff. That seems to me to be
what the embedded team is working on. Once the default embedded protocol is
set, other protocols can be added on without any interference with the core
database. These different protocols, like JDBC, can be totally independent
of the main database work (although some sort of RMI implementation would
probably come standard along with embedded to allow the xindice command line
tool to work).
An Axis SOAP interface would then become an optional separate or sub-project.
The CORBA interface would become an optional separate or sub-project. Those
who don't need a CORBA listener won't build and/or run it.
The point I'm trying to make is, my impression is that, with the embedded
initiative, Xindice is already headed toward being able to run in a servlet
engine if that's where someone wants to run it. That's most likely where
I'll run it. But that shouldn't be the only place it may run. (Is that what
you're asking by "moving Xindice to run under a servlet engine"?)
--
Michael Westbay
Work: Beacon-IT http://www.beacon-it.co.jp/
Home: http://www.seaple.icc.ne.jp/~westbay
Commentary: http://www.japanesebaseball.com/forum/
