[Seaside] Re: i10n or speed?
Klaus D. Witzel
klaus.witzel at cobss.com
Mon Mar 19 15:40:26 UTC 2007
On Mon, 19 Mar 2007 11:58:11 +0100, Philippe Marschall wrote:
> Have you ever tried a counter in a recent version of Seaside? I don't
> know about you but for such a simple application it is way too slow
> for my taste. As part of the 2.8 cycle we look into ways of making
> Seaside faster.
> Attached you will find several traces for the counter application.
> As you can see, an awful lot of time is spent to convert URLs to
> String. Of that most time is spent in#encodeForHTTP.
I know how to speed up #isSafeForHTTP :) Could you make me the traces
again, with the following "correction": there seems to be an #ensure: (at
the top of tree) which seems to obscure, what details are touched by
#encodeForHTTP and #isSafeForHTTP.
> So what do you find more important, that Seaside is fast or that is
> supports non-ascii urls?
> P.S.: the original mail had several traces more but was apparently too
> big, maybe it will arrive later.
More information about the seaside