[Seaside] [CONFUSED]: WAKom, WAKomEncoded or WAKomEncoded 3.9

Lukas Renggli renggli at gmail.com
Wed Feb 11 09:58:33 UTC 2009

> 1) What's the differnece between WAKom, WAKomEncoded and WAKomEncoded39? I
> read the class comments but do not really understand the issue. In addition
> they are dealing with 3.8 vs. 3.9 and I'm on 3.10... If somebody advises me
> to deploy on 3.9 I'll do - I just need a working configuration.

WAKom does no conversion at all. So if you assume that the browser
side uses UTF-8 then you end up with UTF-8 strings inside your image.
However since the internal encoding of Squeak is *not UTF-8* many
strings will appear scrambled when looking at them using an inspector.
It works well though as long as you do not perform heavy string
scrambling, because the strings are sent back as is. If you have
string literals with foreign characters in your application code you
need to make sure that these are valid UTF-8 as well. This is very
efficient, but you need to be aware of the implications.

WAKomEncoded converts incoming data from UTF-8 to the internal
encoding of Squeak, as well it converts outgoing data from the
internal encoding to UTF-8. Like this, all strings are valid from
within the image, and common string operations like #=, #size and
#copyFrom:to: work like you would expect. If you use an external
database that expects UTF-8 you need to convert again.
Since there all incoming and outgoing data needs to be converted, this
approach is slightly less efficient.

WAKomEncoded39 is for compatibility with strange versions of Kom and
Squeak. You should not need to use it.


Lukas Renggli

More information about the seaside mailing list