> You have seen http://openlayers.org/dev/examples/tilecache.html , right?
Indeed. That's what I mimicked, which gave me some bizarre errors. They were so weird (the GeoRSS layers vanishing) that I thought to ask first before putting too much effort into it. > At some point, it's not how fast the server can get the tiles: it's how > much bandwidth you have to fetch them (and, to a sometimes much greater > extent, how big they are to begin with). Optimizing your images can > squeeze a lot more apparent speed out of the same server... You're absolutely right. At present, I'm generating 24-bit PNGs without interlacing. PNG24 is my favorite, as it has both color fidelity (unlike 8-bit formats reading from remote WMS, yuck!) and transparency (unlike JPG) and pretty great quality to boot. Each tile (standard 256x256) is between 3500 and 5100 bytes, which I figure is pretty decent, and it's pretty zippy. Any comments would be welcome, of course. -- Gregor Mosheh / Greg Allensworth System Administrator, HostGIS cartographic development & hosting services http://www.HostGIS.com/ "Remember that no one cares if you can back up, only if you can restore." - AMANDA _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
