Hi guys,

I want to build a server under Squeak that will be constantly listening 
to request on a particular TCP port. Once a request is received, it 
should do what it needs to do (whether it is to lookup something in a 
database and/or return some data back through the same socket) and then 
close that connection and get ready for the next one.

The problem I see is that I expect to receive anywhere between 30-120 
connections per second. The connections are very short (may be 1-2 
seconds max). If I were doing it in Java, I would spawn a child process 
to handle a particular connection while the main server continues to 
listen on the socket.

How would you recommend I approach this in Squeak? I know we have 
talked to great extent about the real need of multi-threaded/process 
applications and the fact that they may not really be needed in Squeak 
(or Smalltalk for that matter), but I don't see any other way to make a 
Squeak box scale to this load. To make things even worse, I don't even 
know which class to look at to get started.

Any help and suggestions would be greatly appreciated.

Thanks,
Daniel