Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43537700.7090700@mobilebox.pl>
Date: Mon, 17 Oct 2005 12:03:44 +0200
From: Leszek Gawron <lgawron@mobilebox.pl>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Problems with lazy loading components
References: <43535F3B.8040402@nada.kth.se> <4353627E.1070403@apache.org>
In-Reply-To: <4353627E.1070403@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:
> I'm actually not sure what lazy loading really gives us? Ok, Cocoon
> starts faster, but if you have just configured the blocks you need I
> think there is not really a difference. And if you need the components
> anyway, you have to wait for them to be setup - being it lazy or not.
Oh I think it gives you a lot. At least from marketing POV. I see all 
the time users are building a WHOLE cocoon just to use core and a single 
block. Long startup times may discourage them in terms of agile 
development before they realize the problem lies in their approach and 
not cocoon itself.

I'm not following block development very precisely (mostly because of 
it's complexity that I do not full understand). I have one question 
though: could whole cocoon blocks be also lazily loaded - just as 
eclipse plugins are (or maybe we have this feature OOTB when using OSGi)?

-- 
Leszek Gawron                                      lgawron@mobilebox.pl
IT Manager                                         MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65