[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] Re: IO and Process Scheduler
From: |
kraehe |
Subject: |
Re: [Help-smalltalk] Re: IO and Process Scheduler |
Date: |
Sat, 4 Jun 2005 01:02:37 +0200 |
User-agent: |
Mutt/1.5.9i |
Moin Paolo Bonzini,
> What OS are you using? The scheduler works under Linux and MacOS at least.
smalltalk-2.1.10 on a Debian Sarge system running Linux 2.6.11.7
skas3-v9-amd32 kernel.
Take a look at, www.copyleft.de/Parla/GST-Network.st and try:
loader.st
Namespace current: Smalltalk!
PackageLoader fileInPackage: 'TCP'!
Smalltalk addSubspace: #MUD!
Namespace current: MUD!
FileStream fileIn: 'GST-Network.st'!
Namespace current: Smalltalk!
to start it :
st> MUD.MUDServer new port: 4321; start!
'register server socket'
'waiting for connection'
MUDServer new "<0xb3d54b10>"
now `telnet localhost 4321` - but nothing happens, if you type
something - the accept is blocked by console, besides using
forkAt: - now type something in smalltalk :
st> 1!
'accepting connection'
'>$t'
'>$e'
'>$s'
'>$t'
'>$
'>$
'
'waiting for connection'
1
st>
replacing start at the command line and in MUDServer>>run with run
will provide a single process telnet server that works fine. Replacing
start with run in the command line, but not in MUDServer>>run will
create a funny situation. At first it works, so its possible to
connect and even to type a line. But the next line is not read.
The client process hangs waiting for IO that already arrived, till
I open a fresh connection to trigger something in the main process.
Bye Michael
--
mailto:address@hidden UNA:+.? 'CED+2+:::Linux:2.4.29'UNZ+1'
http://www.xml-edifact.org/ CETERUM CENSEO WINDOWS ESSE DELENDAM