[OpenLayers-Users] optimizations to deliver openlayers js faster?

[Christopher Schmidt]

On Tue, Jan 09, 2007 at 05:22:06PM -0500, Chris Holmes wrote:
> 
> 
> Christopher Schmidt wrote:
> >On Tue, Jan 09, 2007 at 03:35:26PM -0500, Chris Holmes wrote:
> >>Hey guys, we're contemplating putting a little demo similar to the one 
> >>on openlayers homepage on the GeoServer homepage.  But my concern is 
> >>that the javascript loading can be a bit slow.
> >
> >Is this a concern you've seen from the OpenLyaers home page, or other
> >pages? The OpenLayers homepage is using:
> > * gzip encoding (post-filter in Apache2) of the javascript
> > * Single file build 
> 
> No, not at all.  Sorry, should have stated more clearly.  Was mostly 
> looking to figure out exactly what you guys were doing on OpenLayers 
> homepage.
> 
> > 
> >If this isn't enough for you, it is possible to build a much smaller
> >single file build via Build Profiles:
> >http://trac.openlayers.org/wiki/Profiles   
> 
> Cool.
> 
> >
> >>What's the most efficient way to deliver the javascript so it loads up 
> >>quickly?  Do I gzip it somehow?  Put it all in one file?  Have it load 
> >>modularly?
> >
> >python build/build.py in 2.3+ or build/build.sh in 2.2- are the ways to
> >build a single file version -- alternatively, use the hosted API, which
> >does this, and also has the nifty apache setup, for you.
> 
> Thanks!  It sounds like the easiest thing is to just use the hosted 
> file.  /me crosses fingers for 2.3.0 hosted version soon (I can function 
> without it though).

There is an RC1, but there are outstanding bugs with RC1 that I haven't
fully reviewed before we can do an RC2, and I like to wait several days
before RC -> Final status. If you have specific things you'd like to see
changed/improved for your demo, I can help you add Javascript to your
application code to add functionality that you need from 2.3 in a 2.2
application.  Let me know.

Regards,
-- 
Christopher Schmidt
MetaCarta