Hello Andreas,

it's correct, if you start the server the stuff runs one. After interrupt, show the instances of Socket - you will get one. But if you started the server with fork (all instances of Socket must be deleted from image before) and you check the instances, you will get more than one.

Steffen

-----Original Message----- From: Raab, Andreas [mailto:Andreas.Raab@disney.com] Sent: Freitag, 9. Juni 2000 10:04 To: squeak@cs.uiuc.edu Subject: RE: Start sockets via fork creates 2 instances?

Steffen,

I don't seem to be able to recreate your problem. I tried the #remoteTestServer and - having a Transcript open - it showed that the stuff gets only run once. Just as an aside I can't see any reason why two instances of Socket should be created. Perhaps you're just not looking at the right thing?! What gives you the impression that two sockets are created?!

- Andreas

PS. Feel free to drop me a mail off list if you got any more trouble.

-----Original Message----- From: Steffen.Mueller@phaidros.com [mailto:Steffen.Mueller@phaidros.com] Sent: Friday, June 09, 2000 12:48 AM To: squeak@cs.uiuc.edu Cc: recipient list not shown Subject: Start sockets via fork creates 2 instances?

Start sockets via fork creates 2 instances?

Hello

I trying to develop a server-application via sockets. To serve more than one requests, I started the server with 'forkAt: Processor highIOPriority' and I got 2 instances of Socket! The example-implementations of Socket ([Socket remoteTestServerTCP] forkAt: Processor highIOPriority) works same. Starts the server without 'forkAt:', only one instance will be created. Is this the correct behavior?

Thanks in advance for your ideas Steffen