Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 9659 invoked by uid 500); 9 Jan 2003 09:21:30 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 9645 invoked from network); 9 Jan 2003 09:21:29 -0000 Message-ID: <3E1D3F1E.8080905@interface-projects.de> Date: Thu, 09 Jan 2003 10:21:34 +0100 From: Jens Lorenz Organization: interface:projects User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.2.1) Gecko/20021130 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Defining Source Interfaces References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stephan Michels wrote: > >>>>About the move() and copy() methods, I don't know if they should be kept >>>>in the new incarnation of this interface. >>> >>>:-/ not another MoveableSource ;-) >> >>ROFL !!! > > ;-) > >>Seriously, are these methods of real use ? > > I thought that these methods could be a good start for a cms > webportal. Not? I agree with you, Stephan. This is an excellent start for a CMS. CMS-wise you can't think of Sources as files. It's a file with metadata which you need in order for your CMS to work. If you treat them just as files you will loose those metadata and your CMS will start choking at the next user interaction. Jens -- Jens Lorenz interface:projects GmbH \\|// Tolkewitzer Strasse 49 (o o) 01277 Dresden ~~~~oOOo~(_)~oOOo~~~~ Germany --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org