Return-Path: <PNarula@directsourcing.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 28948 invoked from network); 24 Jan 2000 15:11:43 -0000
Received: from proxyserver1.directsourcing.com (HELO
 proxyserver1.directsourcing) (12.30.176.37)
  by 63.211.145.10 with SMTP; 24 Jan 2000 15:11:43 -0000
Received: by PROXYSERVER1 with Internet Mail Service (5.5.2448.0)
	id <D3QTBGX8>; Mon, 24 Jan 2000 10:00:05 -0500
Message-ID: <CE9B5F3B4465D211A980002035E77C15016D835C@PROXYSERVER1>
From: PNarula@directsourcing.com
To: cocoon-dev@xml.apache.org
Subject: Cache
Date: Mon, 24 Jan 2000 10:00:03 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

Here are my two cents on Cache

Yes Cocoon is a dynamic publishing framework, but how dynamic a site would
be. Let's take an example of a typical site which serves output depending on
the client. Site content is stored in xml. Most of the time maximum hit a
site would get is the main page. Won't it make sense to just keep it stored
in the requested format(html,wml etc.) and just check if the source xml has
changed. External file inclusion makes more sense over here. 

Pankaj