[Seaside-dev] Seaside 3.0a6ish

[Julian Fitzell]

On Thu, May 20, 2010 at 6:32 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2010/5/19 Michael Lucas-Smith <mlucas-smith at cincom.com>:
> > The expectation of the GRCodec is that, unfortunately, you will get back
> a
> > String object no matter whether you're doing an encode: or a decode: .. I
> > would *LOVELOVELOVE* to return a ByteArray when you call #encode: - but
> this
> > has never worked because Pharo/Squeak could never do it. May be this has
> > changed, but none of the code that calls #decode: gives us a ByteArray -
> all
> > of the tests, examples, seaside actual code passes in a String containing
> > characters representing bytes. I would really love it if the API had a
> > contract like this:
> >
> > GRCodec>>encode: (String)
> >    ^(ByteArray)
> >
> > GRCodec>>decode: (ByteArray)
> >    ^(String)
>
> I agree. I believe the first one is doable, I'll hack together a
> prototype today. The second is more tricky because the servers
> themselves (Comanche and Swazoo) already give us a String which is
> actually just a ByteArray.
>
> Maybe we could get the servers "fixed" (might imply a mode you can set or
something). Obviously the server adaptors can simply deal with it as well,
but there's going to be an inefficiency there.

Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100520/31761966/attachment.htm