RE: Tomcat or PHP in ST ?

> -----Original Message-----
> From:  azgolfer
> [...]
> I think the main thing is to get something like Tomcat up and running.
> I don't think continuations are important at all. I'm curious about
> how difficult it will be to get a multithreaded application server for
> ST. Does "supports native threads" mean you are writing C++ code to
> implement a multithreaded server ?

No, it means that each Smalltalk process runs in its own native thread,
although they are non-preemptively scheduled from Smalltalk.  This allows
callouts to be designated as asynchronous, which lets them do blocking I/O
while other Smalltalk processes are allowed to proceed; when the blocking
callout finishes and tries to return to Smalltalk, it then waits until it is
scheduled again from Smalltalk to continue.  The practical implication of
this is that blocking callouts are trivial, unlike in other Smalltalks.  One
visible example of this is that message boxes and and modal dialogs in the
GUI (which are blocking C callouts) are modal only for their parent
application process, as it should be.

The biggest missing piece for a (non-preemptive) multithreaded server is
that there is no network socket/stream implementation right now.  That would
be a good project if someone wants to fiddle with the Strongtalk image in a
useful way.

-Dave


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---