Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Message-Id: <008a01c2d345$24893090$2e64a8c0@majesty>
Reply-To: "Clemens Marschner" <cmad@lanlab.de>
From: "Clemens Marschner" <cmad@lanlab.de>
To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
References: <8529F6E7-3DFB-11D7-AC84-000393B3D1F4@simpledesign.com>
Subject: Re: [LARM] Merlin and other additions
Date: Thu, 13 Feb 2003 10:49:03 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

very cool, thanks, David.

+1 that we put this into lucene-sandbox/projects/larm and use it as a basis
for our developments.

+1 that we David gets commiter access to lucene-sandbox

Clemens

----- Original Message -----
From: "David Worms" <david@simpledesign.com>
To: <lucene-dev@jakarta.apache.org>
Sent: Tuesday, February 11, 2003 9:00 PM
Subject: [LARM] Merlin and other additions


>
> --> http://67.116.155.180/~wdavidw/larm.zip
>
> OK, here is the status.
>
> o distribution include source codes, binaries and maven scripts.
>
> o Larm is now using Merlin as a container. The reasons behind this move
> is greater architectural flexibility and cutting edge:)
>
> o All services/components are well isolated, the interfaces are
> separated from their implementations by packages.
>
> o The old Monitor service is split into 3 services. The Monitor service
> itself, performing monitory task (only a small one right now). The
> Descriptor service (basically our old Monitor stuff). Finally there is
> a Printer service which I really want to see removed and replace by a
> client application connecting to the larm through AltRMI. I have tried
> to use AltRMI but lost patience. Using the version 0.7 with phoenix, I
> know it work great and is easily embedded inside a component
> architecture (facade pattern).
>
> o Cornerstone components are loaded into Merlin. Not successful with
> AltRMI but it could be really useful if we want to use the threadpool,
> scheduling, ..., services.
>
> o License and basic javadocs are included.
>
> TODO:
>
> o Create  a Parser service. It will be mapped around the current
> "Tokenizer" class. Not completely sure but I think only a "parse(
> LinkHanlder lh, Reader r )" function have to be exposed.
>
> o AltRMI
>
> o Use the Cornerstone Thread service. Will lead to many changes.
>
> o Use the Excalibur event service.
>
> David
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org