For a general admin tool I guess the webapp path is the best way to go.

I like the concept of the Eclipse plugin
(org.apache.xindice.tools.ui.eclipse) I would like to provide some input
to that project but I donīt know who to get in contact with...

Cheers
Sten

-----Original Message-----
From: STONE,ROBERT (HP-SanDiego,ex1) [mailto:[EMAIL PROTECTED] 
Sent: den 11 april 2003 20:35
To: 'xindice-users@xml.apache.org'
Subject: RE: Best Client for Viewing/Editing Xindice 1.1?

I would guess that one can take xmldbgui code and extend it to have web
interface. However I don't know if xmldbgui license will allow it. I'll
try
to look into it

Bob Stone


-----Original Message-----
From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2003 11:31 AM
To: xindice-users@xml.apache.org
Subject: Re: Best Client for Viewing/Editing Xindice 1.1?


> I looked at the whole servlet for a little bit. Its an interesting 
> solution, XML-RPC through the POST requests and html'ized viewing 
> through the http GET requests. There are definitly some shortcomings 
> with at least the http GET side of the XindiceServet. One thing I
don't 
> like was the "buffering" of the query results into a byte[]. Wouldn't
it 
> be possible to "Stream" to response.out to improve memory use and 
> performance on viewing large result sets/documents?

What I did was a HUGE hack.  It's hugly, hugly, hugly (wonder why I
named it
the
"ugly debug tool"?)  I have no experience with Servlets and this was my
first
quick-and-dirty attempt.  I promise Iwon't feel offended if you say that
this
code is &^%$^ because I'm the first one to say that! :-)

> Having it all in one servlet is a little monolithic. I think the
design 
> should be considered inadequate for Admin purposes. There are alot of 
> different tasks an Http based admin service is going to need to
provide, 
> theres going to be varying security related issues that need to be 
> resolved for Access Control etc, a design strategy should probibly be 
> planned and well thought out.

Currently the problem of Xindice is not security related.  It's admin
related. 
Xindice is not admin-friendly and a simple admin tool is really needed.
At
the
beginning you can simply restrict the access to the local machine.

I would prefer to see some code working than yet another architecture
draft.

It's always possible to refactor but you need to have some code first.

-Vladimir

-- 
Vladimir R. Bossicard
www.bossicard.com

Reply via email to