[Seaside] i10n or speed?
ssastre at seaswork.com
Thu Oct 4 18:36:26 UTC 2007
What drawback(s) non-ascii url will provide? What we loose by choosing that?
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Philippe Marschall
> Enviado el: Lunes, 19 de Marzo de 2007 07:47
> Para: Seaside - general discussion
> Asunto: [Seaside] i10n or speed?
> 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.
> So what do you find more important, that Seaside is fast or
> that is supports non-ascii urls?
More information about the seaside