[Seaside-dev] about Grease codecs

[Julian Fitzell]

Yeah, we decided to leave really solving encoding issues for 3.1. But
I agree that you should be able to deal with encodings in terms of an
internal/external encoding pair (even if the internal is "native" in
most cases).

The idea was that a "null" encoding would still require to specify an
encoding, it would just be the same on both sides. That way the
external encoding of the adaptor could be used as the default when
setting headers and so on in the request (rather than having to
specify it also as an application setting).

Julian

On Tue, Mar 30, 2010 at 8:07 AM, Lukas Renggli <renggli at gmail.com> wrote:
>>> As far as I know Pharo and Squeak has no way to convert between two
>>> arbitrary codecs. You always have to go through the internal encoding
>>> first.
>>
>> This doesn't mean Grease couldn't provide a method to do the
>> triangulation.  It can be twice as fast in other dialects.
>
> Yeah, we had long discussions about that last ESUG. AFAI, we came to
> the conclusion that in practice this is rarely useful so we won't
> support it for now. I see however that adding a factory method for
> arbitrary codecs could be cool, if you propose a change we can
> certainly integrate that.
>
> Lukas
>
> --
> 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
>