[Seaside-dev] what happened to WASqueakUtf8Codec?

[Philippe Marschall]

2009/2/15 Lukas Renggli <renggli at gmail.com>:
> I did not bother rewriting that number crunching beast.

It's more than 400 (four hundred) times faster for ASCII and about
three times faster for Latin-1.

> Feel free to embed it into its own stream class if you think that's useful.

Is there somewhere a documentation of the expected protocol?

Philippe

> Lukas
>
> On Sun, Feb 15, 2009 at 11:21 AM, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
>> It contained a much optimized UTF8 encoding algorith that was much
>> faster than the default UTF8TextConverter. Second I'm unhappy with
>> GenericCodec >> #url. Just because some document somewhere says
>> something that doesn't mean nothing. If you run ISO-8859-1 then your
>> URL encoding will be ISO-8859-1 no matter what specs and Wikipedia
>> entries say.
>>
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>