Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of awiner@gmail.com designates
 64.233.184.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=uBh4a71uYJK/43dSNoNIIWcNlbbPGWK1ywCx9SXUUWxTVD7BU4UoBB/+e0zexzPVLlh6lLDFmCdUC7Z0J2xGdQRyEOsfueLwmpeOrLoQmXxE3ipUy4mQA4f3Buhl/QIcrf0n8mtdyq50HxCkYRd1nlHDE2GMWFmAbZMVGRbQYHU=
Message-ID: <6dac79b90601032138l532babfj768e36d9beba4e75@mail.gmail.com>
Date: Tue, 3 Jan 2006 21:38:05 -0800
From: Adam Winer <awiner@gmail.com>
To: MyFaces Development <dev@myfaces.apache.org>
Subject: Re: Prototype library and portlets
In-Reply-To: <dpek5s$8i4$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <dp1g4o$e05$1@sea.gmane.org> <dpdrir$cse$1@sea.gmane.org>
	 <5a99335f0601030529t5ce41f70r855b514365b4ff29@mail.gmail.com>
	 <dpe14u$u7v$1@sea.gmane.org>
	 <5a99335f0601030624q76f12ddfyb70dbe955918a42e@mail.gmail.com>
	 <dpe8ao$oft$1@sea.gmane.org>
	 <16d6c6200601030928g7281c672wafc68c8a7fbe4b4f@mail.gmail.com>
	 <dped9d$eav$1@sea.gmane.org>
	 <16d6c6200601031007t177ca6dcme48e1173aed072c@mail.gmail.com>
	 <dpek5s$8i4$1@sea.gmane.org>

Werner,

ADF has some technology that may be helpful here (when
it arrives, grumble, grumble...)

http://tinyurl.com/999qe
http://tinyurl.com/7vn42

Cheers,
Adam


On 1/3/06, Werner Punz <werpu@gmx.at> wrote:
> Actually this all or nothing or common ground approach is not what I had
> in mind.
>
> What I am thinking of is something along these lines.
> You already have some kind of dynamic loading infrastructure in there
> with
>
> dojo.require("dojo.a");
> dojo.require("dojo.b");
>
> now the problem as discussed is that this triggers
> xmlhttp requests and is slow
>
> the alternate solution to this dynamic linking is a static linking via
> an ant build to drop everything into a single file.
>
> Also bad, because one time you download a single huge file (well
> compresset but still)
>
> This is a viable approach for a webapp but not for a component library
> where one component needs part a of dojo and part b and another one
> needs part a and c.
>
> The infrastructure is there to make dynamic includes upon the given
> needs of the components currently used.
>
> So theoretically if only one component is loaded than an include of part
> a and b is done.
>
> If the second one is added an additional one for part c also is done.
>
> It is sort of a semi dynamic linking where myfaces adds the needed
> includes and neither the build system nor the javascript runtime.
>
> You get the benefits of both approaches that way, less code download
> because only the parts needed are loaded and still excellent browser
> caching, due to standard javascript includes.
>
> So my question, does dojo already support such an approach?
>
> Werner
>
\