The current LCF standard deployment model requires a number of moving parts,
which are probably necessary in some cases, but simply introduce complexity in
others. It has occurred to me that it may be possible to provide an alternate
deployment model involving Jetty, which would reduce the
@incubator.apache.org
Subject: Proposal for simple LCF deployment model
The current LCF standard deployment model requires a number of moving
parts, which are probably necessary in some cases, but simply introduce
complexity in others. It has occurred to me that it may be possible to
provide an alternate
rid of the database requirement is also obviously not an option.
Karl
--- original message ---
From: ext Jack Krupansky jack.krupan...@lucidimagination.com
Subject: Re: Proposal for simple LCF deployment model
Date: May 28, 2010
Time: 10:42:17 AM
A simple deployment ala Solr is a good goal
: karl.wri...@nokia.com
Sent: Friday, May 28, 2010 11:10 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Proposal for simple LCF deployment model
You forget that building lcf in its entirety requires that you supply
proprietary client components from third-party vendors. So i think
PM
To: connectors-dev@incubator.apache.org
Subject: Re: Proposal for simple LCF deployment model
But for a basic, early evaluation, test drive, just the file system and
web repository connectors should be sufficient. And if there is a clean
database abstraction, a basic database package (e.g
@incubator.apache.org
Subject: RE: Proposal for simple LCF deployment model
I've been fighting with Derby for two days. It's missing a significant
amount of important functionality, and its user and database model are
radically different from all other databases I know of. (I'm also getting
nonsense
operation.
Karl
--- original message ---
From: ext Jack Krupansky jack.krupan...@lucidimagination.com
Subject: Re: Proposal for simple LCF deployment model
Date: May 28, 2010
Time: 10:33:34 AM
(b) The alternative starting point should probably autocreate the
database,
and should also
To: connectors-dev@incubator.apache.org
Subject: Re: Proposal for simple LCF deployment model
(b) The alternative starting point should probably autocreate the
database,
and should also autoregister all connectors. This will require a list,
somewhere,
of the connectors and authorities
--
From: karl.wri...@nokia.com
Sent: Friday, May 28, 2010 11:16 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Proposal for simple LCF deployment model
Dump and restore functionality already exists, but the format is not xml.
Providing and xml dump
