Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Moving reduced version of CachingSource to core | Configuration
 issues
Date: Tue, 27 Mar 2007 10:43:39 +0200
Message-ID: <A955EA1F8FE31749AEC8C998082F6C7CD6E90D@webmail.hippo.nl>
Thread-Topic: Moving reduced version of CachingSource to core | Configuration
 issues
Thread-Index: AcdvwcEeRnCjpy//Tk676yqIGq99WAAh52Gg
From: "Ard Schrijvers" <a.schrijvers@hippo.nl>
To: <dev@cocoon.apache.org>


> Vadim Gritsenko wrote:
> > Oops, should have read it in full...
> >=20
> > Reinhard Poetz wrote:
> >=20
> >> I can think of setting the expires parameter to -1 and using a
> >> background-refresher but this seems to be overly complex for this=20
> >> simple task.
> >=20
> > Yes async will do the trick. And IMHO it should be Ok to alter sync=20
> > implementation to keep previous response if new one can't=20
> be obtained.
>=20
> sounds easier than Ard's proposal (no offense ;-) ), or do I=20
> overlook something?

That certainly is a *lot* easier and I was not aware of this part in the =
cachingsource! Might be useful for me as well :-)=20

Ard

>=20
> >> I would also like to move the basic functionality of the=20
> CachingSource=20
> >> into some core module and only have an extended versions=20
> (event-cache=20
> >> support, async updating) of it in the reposistory block. I=20
> seems odd=20
> >> to me that I have to add a dependency to the repository block, the=20
> >> event-cache block, the jms block and the cron block
> >=20
> > I do not think it has any dependencies on cron, where do you see it?
>=20
> either it comes through a transitive dependency or I did=20
> something wrong with my=20
> setup. I will check where it comes from.
>=20
> >> just for this. Any comments before I start a vote on this?
> >=20
> > Async is a basic functionality which must be in core, IMHO. But I=20
> > completely agree that event-cache and jms should be optional. I was=20
> > planning on doing this refactoring but did not manage to do=20
> it so far.
>=20
> It would be great if you could help me with the design of the=20
> refactoring: If=20
> you did it, into which parts would you split it up?
>=20
> --=20
> Reinhard P=F6tz           Independent Consultant, Trainer & (IT)-Coach =

>=20
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
>=20
>                                         web(log): http://www.poetz.cc
> --------------------------------------------------------------------
>=20