Return-Path: 
 <dev-return-46628-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 55359 invoked by uid 500); 21 Aug 2003 11:29:13 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 55332 invoked from network); 21 Aug 2003 11:29:13 -0000
Received: from pop018pub.verizon.net (HELO pop018.verizon.net)
 (206.46.170.212)
  by daedalus.apache.org with SMTP; 21 Aug 2003 11:29:13 -0000
Received: from verizon.net ([138.88.97.20]) by pop018.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030821112725.MKII11703.pop018.verizon.net@verizon.net>
          for <dev@cocoon.apache.org>; Thu, 21 Aug 2003 06:27:25 -0500
Message-ID: <3F44AC94.2080108@verizon.net>
Date: Thu, 21 Aug 2003 07:27:16 -0400
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] Improving Views
References: <CA2558DD-D2ED-11D7-B0BD-000A278D3A84@leonid.de>
 <3F43434A.8080303@upaya.co.uk>
In-Reply-To: <3F43434A.8080303@upaya.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from
 [138.88.97.20] at Thu, 21 Aug 2003 06:27:25 -0500
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Upayavira wrote:

> leo leonid wrote:


<snip/>

>> I think it is not sufficient to have views that can be 
>> enabled/disabled. Sometimes other components depend on certain views 
>> (like the Lucene indexer) and so you can't disable. Maybe we need a 
>> sort of access restriction mechanism.
>
>
> Like <map:pipeline views="internal"> or <map:pipeline 
> allow-views="x,y" internal-views="a,b">?
>
> The same would apply to the command line/bean, which requires link 
> view, but which you might not want to expose to the public.


Those views actually were intended to be exposed to the public. So 
public can intellegently crawl your website, or aggregate parts of your 
website, or index your website (think search engine which indexes 
content, not navigation bar). So Cocoon running on the user's host could 
interoperate with another Cocoon instance on another host.

But yes, sometimes you may want to disable this view here or that view 
there.

Vadim