Bug #19
more than one connection causes wierdness
Start date:
2008-04-18
Due date:
% Done:
100%
Estimated time:
Description
If the first connection is in the menu and a new connection arrives, it hangs.
If the first connection is talking to a serial port and a new connection arrives, then the first connection is terminated
Associated revisions
History
Updated by Hamish almost 15 years ago
- Subject changed from wconsd cannot handle two connections at the same time to more than one connection causes wierdness
Updated by Hamish almost 15 years ago
- % Done changed from 0 to 30
There is less weirdness here now, but it is still not actually accepting more than one connection. The framework has been built to support multiple connections but the existing serial-data-pump logic is still using the old system
Updated by Hamish almost 15 years ago
- Status changed from New to Closed
- % Done changed from 30 to 100
Using the new connection model mostly fixes this problem. Any future issues should be considered a regression
Migrate threads to new connection model, allowing multiple connections.
This is the first part of migrating the two threads to use the new
connection table. This change also rips out a lot of the event waiting
system. All the unused variables are going, but I have not yet looked
at removing these events. It still remains to cook the net data for
CL NUL and IAC options. refs #19