A while ago, we introduced ConnectionHandler to Comanche, so that we
could develop our own scheduling/dispatching mechanisms, etc. But this
never came to be (at least not in the so-called "GaTech Comanche", it
could've happened in NetUnify's Comanche).
So, we're going to test and see if having our own ConnHandler is
better than using ConnQueue. The attached change set creates two
classes PWSComancheServer and PWSComancheService that use ConnQueue.
(Note that there's only one method in Service, to make sure it
references the correct Server class -- this needs refactoring).
This change set also adds Socket initializeNetwork to #start method of
ComancheServer.
In kom47, you can try to do:
svc _ (PWSComancheService named: 'Comanche' onPort: 8080) module:
(RemoteDisplayModule new).
svc start
To stop all that madness, do these:
ComancheNetService removeServiceNamed: 'Comanche'.
| che | (che _ ComancheServer serverOnPort: 8080 ifAbsent: [])
ifNotNil: [che stop]
This is provided so that you can have fun with this too.
Bolot
kom47-base (sans kom47-beyond) can be found at:
http://fce.cc.gatech.edu/~bolot/squeak/comanche/kom47-base.16Jan1158.cs.gz
