[Newbie] Is squeak thread-safe ?

Guillaume Rams guillaume.rams at sema.fr
Thu Dec 16 16:08:57 UTC 1999


>
> The squeak VM doesn't use threading facilities from the operating system.
> It implements its own "threads" in user space.
>
Bad news.

>
> Is this supposed to be executed on the client?
> That would open huge security holes, you know...
I guess that if the image is stripped of all "platform glue" classes (file
system, memory access and all the like) it would be safe enough.
If one could define new classes in his "scripts", I guess that I would have
to check that it uses no "dangerous" primitives. Hmm... :-(

>
> On *nix, you can compile with the HEADLESS option. Then all the X stuff
[...]
Oh I see. The command-line only squeak is called "HEADLESS" ?

>
> Pardon the ignorance: what is COM?
Ooooops, sorry :-) This is Microsoft components. Win32 specific again :-(.
I'm affraid that, in order to communicate with "objects" of the environment,
I will have to send messages to a COM object. Or ActiveX. Microsoft's
terminology is really obscure (to me at least). I'm not a specialist of this
stuff. That's why I need help ;-)
What I had in mind is to have some kind of factory that will instanciate a
wrapper class for each kind of COM insterface. Then override
"doesNotUnderstand" to try to send the message to the wrapped object. Quite
ugly, isn't it ? Better idea someone ?

Guillaume Rams





More information about the Squeak-dev mailing list