On Thu, 18 Jul 2002, Kimbro Staken wrote: > >On Thursday, July 18, 2002, at 09:37 PM, Michael Westbay wrote: >> >> 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"?) >> > >What I was referring to is simply that Xindice has to this point always >been considered a server. Because of this we need to continue to ship >something that runs as a server, so we need to pick a mechanism to enable >that. This doesn't in any way limit other ways of running it, in fact it >should make it quite clear that it is simple to create a custom server if >you want. The current code is too complex, so complex in fact that most >people didn't even know that you could run Xindice embedded, or that you >could run it in another server environment. I'm not exactly sure what >format we'll ship things in, but we have to ship some form of server and I >don't want to continue using the current overly complex code to do it. >This is what I meant, it should be perfectly in agreement with what you're >saying. At least that is my intention. Also once we update the >documentation there will be a much greater focus on embedding and general >flexibility so hopefully it will be clear that there isn't just one way to >do it. In the past that definitely wasn't clear. > >> -- >> 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/ >> >> >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 >
What I would see is some server engine which isn't able to run at its own. It would need some running environment. This could be either a server bed to make a standalone server or a servlet bed to have it as a servlet. Or a embedded bed (if this is even an extra situation) to have it able to run in some other applications embedded. So people see how to make a bed/proxy for running the Xindice engine in different environments. For eample command line interface or connection by CORBA, SOAP, XML-RPC, HTTP or Socket. This could be seen as a connection plugin or as a running plugin or two seperate plugins as well. These plugins are not really part of Xindice itself they exist more like a demo or example or as some testcases. Then I could see some authentication, authorisation or accounting plugin or a simple access plugin. Sure, these points are issues from xmlBlaster also, but I see lot's of parallel requirements for both core engines. People want to connect in many ways. Every user has different environments. Unfortunately they not all working with Java ;-) (But with XML, hopefully) Hope this makes at least some sense to you. kind regards Heinrich -- http://www.xmlBlaster.org
