spaetz <[EMAIL PROTECTED]> writes: > On Fri, Sep 12, 2008 at 11:36:23AM +0200, Jiri Klement wrote: >> It would be indeed better if everything could be handled by >> xslt. But some tasks are too slow and complicated to implement in >> xslt. I think performance was the main reason why or/p is now >> default instead of xslt. > > Of course client performance is good, but it's not critical. The XSLT > version basically is just unmaintained and unmaintainable. That is why > the perl replacement was started.
I think it was also eating up more memory. Since I switched to or/p I have not had any memory problems on any of my clients. (I have memory problems myself, but that's a different subject...) Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
