embedded or directly manipulated?

[Steven Cummings <cu...@netscape.net>]

Hey all,

I've search through the mailing list archives and the source code and I'm not quite sure how I want to approach this, so I thought I'd ask. I've posted to the list before about authentication, but that's too general of a question.

Anyway, I notice that a Kernel is started via Xindice.main and that the main point of access for services is the HTTPServer class. I'm not sure about the glue in-between where the server takes requests, calls scripts (?) and fulfills them. What I'd like to do is close off access to the HTTPServer altogether (by commenting out that service in system.xml) and then directly manipulate the Xindice instance, fulfilling requests as I find appropriate through my own service. I don't see that this has been discussed in the mailing list. I'm sorry if I missed it. I assume this is what people refer to as embedding Xindice (in another app). One approach I've though of is to have my service or Servlet (that provides access to the service) instantiate and maintain an instance of Kernel. I suppose I could then grab the query engine and do what I needed? I'm sorry if this question sounds stupid, I just wanted to make sure I wasn't doing something totally wrong before hitting a dead-end. Thanks.

/S

-- 
Steven Cummings <cu...@netscape.net>
Columbia, MO



__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

Re: embedded or directly manipulated?

["Mark J. Stang" <ma...@earthlink.net>]

I believe that Kimbros new embeded version should do that.   I haven't had a chance
to try it yet.   Has anyone else?

Mark

Steven Cummings wrote:

> Hey all,
>
> I've search through the mailing list archives and the source code and I'm not quite sure how I want to approach this, so I thought I'd ask. I've posted to the list before about authentication, but that's too general of a question.
>
> Anyway, I notice that a Kernel is started via Xindice.main and that the main point of access for services is the HTTPServer class. I'm not sure about the glue in-between where the server takes requests, calls scripts (?) and fulfills them. What I'd like to do is close off access to the HTTPServer altogether (by commenting out that service in system.xml) and then directly manipulate the Xindice instance, fulfilling requests as I find appropriate through my own service. I don't see that this has been discussed in the mailing list. I'm sorry if I missed it. I assume this is what people refer to as embedding Xindice (in another app). One approach I've though of is to have my service or Servlet (that provides access to the service) instantiate and maintain an instance of Kernel. I suppose I could then grab the query engine and do what I needed? I'm sorry if this question sounds stupid, I just wanted to make sure I wasn't doing something totally wrong before hitting a dead-end. Thanks.
>
> /S
>
> --
> Steven Cummings <cu...@netscape.net>
> Columbia, MO
>
> __________________________________________________________________
> Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/
>
> Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

--
Mark J Stang
System Architect
Cybershop Systems