Possibly another way to think about this is to split Xindice into two modules,
core and standalone. The goal of core would be to supply a very high quality
native xml database with very little baggage, that could be cleanly be embedded
into servers such as Tomcat, Avalon, Cocoon or JBoss. The goal of standalone
would be to be a light weight server that embedded the core to provide a
reasonable set of standalone services. This would allow the best of both.

- joel

Kurt Ward wrote:

> Concerning keeping the server as a stand-alone, I would have to say
> definitely a stand-alone server.  Not only community/user base will be much
> smaller if it is not, but there are more ways to use the server in this
> setup
> than there are tied to something else (that might not be needed at all).
>
> Kurt
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
begin:vcard 
n:Rosi-Schwartz;Joel
tel;fax:+44 1435 831011
tel;home:+44 1435 831010
tel;work:+44 1435 831010
x-mozilla-html:TRUE
org:Techne Research Limited
version:2.1
email;internet:[EMAIL PROTECTED]
title:Architect
adr;quoted-printable:;;Downgate Farmhouse=0D=0AFurnace Lane;Warbleton near Heathfield;East Sussex;TN21 9AZ;United Kingdom
fn:Joel Rosi-Schwartz
end:vcard

Reply via email to