[vwnc] Seaside + Opentalk + Windows Mobile = problems

Thanks for the report. We have an AR open for this and we'll hopefully
have a fix included in the product soon. Though Martin Kobetic might be
able to send you a patch so you can continue working from where you are.

Cheers,
Michael

Lautaro Fernández wrote:
> Hi, I'm trying to put a fresh image with Seaside + Opentalk inside of
> a iPAQ (rx5910) and I'm getting some problems (each one has the stack
> attached):
>
> 01)
> The first one was with the message Seaside.SeasideServer
> class(Opentalk.GenericProtocol class)>>setHost
>
> which is as follow:
> #setHost
> HostName := SocketAccessor getHostname.
> HostAddress := " IPSocketAddress hostAddressByName: HostName."
> ByteArray with:127 with: 0 with: 0 with: 1.
>
> To make it "functional" I had to bind the localhost manually, because
> the IPSocketAddress crashed every time I run the image inside the iPAQ.
> Is this approach correct?
> (see stack in attach 01-opentalk.doc)
>
> 02)
> If the port server is set to 7777 (as default) the image also crash.
> When? when it has to validate the host in
> Net.HttpURL(URLwithPath)>>validateHost: . If the port is set to 80 all
> runs ok. (see attach 02).
> The thing that tries to validate is: ���T�E獯
> This is strange, because I'm not an Asian speaker, so those kind of
> characters are never used in my images.
>
> 03) If I want to debug the problem #02, I got an encoding issue with
> the debug's view (see attach 03). It tries to display the Chinese-like
> characters (I'm from Argentina, so this is quite estrange to me) on a
> label.
>
>
>
> So, is all this ( 1, 2 and 3) a whole encoding issue related to the
> Windows Mobile ?
> Did someone try to load Seaside and then run in an iPAQ ?
>
>
> Any hints would be much appreciated,
> Lautaro Fernández
>
>
> iPAQ rx5910 features:
>
>     * 64 MB RAM
>     * 500MB user available
>     * Samsing SC32442 400MHz processor
>     * Microsoft Windows Mobile 5.0
>
> VisualWorks
>
>     * Version 7.6 (clean and fresh)
>     * Parcel CE
>     * Seaside [2.8a1-lr.518 - CW7.6 27]
>     * Opentalk-HTTP [7.6]
>
>
> --
> Luke LAut SkyFernadezWalker

> ------------------------------------------------------------------------
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

Sorry about the garbage in my previous message. This is what I intended to send. Hopefully somewhat more useful :-).

The AR#54332: "[core] We should not initialize GenericProtocol.HostAddress for protocols that don't use proxies (e.g. HTTP)" only concerns the first problem.

I don't know about the other 2, there's not enough details for me to understand what's going on (are you dealing with internationalized domain names ? is IDNA involved somehow ? should be maybe ?).

Anyway, as far as workarounds for the first problem go, your patch is fine. As long as you're using only HTTP, the two globals actually don't matter in that context. Alternative solution, that doesn't require patching code would be preventing the server from autostarting on post-load, setting up the globals manually and then starting the server. Something like.

Smalltalk at: #DoNotStartSesideServer put: true.
Parcel ensureLoadedParcel: 'Seaside' withVersion: nil.
Opentalk.GenericProtocol.HostAddress := #[ your IP].
Opentalk.GenericProtocol.HostName := 'your host name'.
Seaside.SeasideServer start

I haven't tested it, but hopefully it's clear what's meant. The "official" solution will be something along the lines suggested by the AR title.

HTH,

Martin