[Seaside] Swazoo - Improper store into indexable object

Boris Popov boris at deepcovelabs.com
Wed Jul 25 08:41:20 UTC 2007

Point is, the fixes I made are in the glue code, not even seaside, and ones I didn't want to spend time on but kind of had to. I had no such problems on wtk version and that's all I'm saying as far as basic comparison goes. Also, the virtual sites caused me more grief than I wanted as I couldn't find a way to listen on all interfaces like I could with tiny. Again, I was told that it was a useful feature even though I know it wasn't for me. I ended up with an ugly deployment hack there that sets up sites on all local interfaces that I can discover, something I would not have to do with a simpler wildcard broker in front. Please don't take it personally, but if you want swazoo to be a server of choice for seaside, these kinds of things would need to be accounted for, not simply dismissed IMHO.


(Sent from a BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Wed Jul 25 01:30:47 2007
Subject: Re: [Seaside] Swazoo - Improper store into indexable object

Hi Boris,

Boris Popov wrote:
> Together with other fixes I put in to support UTF8 via Swazoo the following seems to do the trick,
> HTTPResponse>>entity: anEntity
>  entity := anEntity isString
>                ifTrue: [anEntity asByteArrayEncoding: #utf8]
>                ifFalse: [anEntity asByteArray].
> Any plans to include support for UTF8 out of the box? I've heard the whole "Swazoo is just a server, 
> its up to you to figure out encodings", but not quite buying it personally having spent some time 
 > hacking it to work ;)

You heard well and I still argue that utf8 is a duty of web framework, 
because it knows better when to convert strings and when not. That 
specially true on the input side. Swazoo just server content as it been 
pure binary. Not doing utf8 is therefore an inefficiency of Seaside, not 
Swazoo, IMHO. And as you actually did already, it is simple to add that 
on output side. Just that you need to do similar on input side too, 
which is a bit more demanding.

Best regards

Janko Mivšek
Smalltalk Web Application Server
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070725/f7e7a5e3/attachment.htm

More information about the Seaside mailing list