You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have one state machine that is used by Catnap and Catloop and then an additional one in the inetstack. This should be deduplicated into one state machine.
Proposed Solution
Add the ability to store state/sockets in the state machine? I think we should be able to store sockets in the state machine and/or addresses depending on the state that the queue/socket is in. This will eliminate the need for the existing state machine in the TCP stack.
The text was updated successfully, but these errors were encountered:
Context
Currently we have one state machine that is used by Catnap and Catloop and then an additional one in the inetstack. This should be deduplicated into one state machine.
Proposed Solution
Add the ability to store state/sockets in the state machine? I think we should be able to store sockets in the state machine and/or addresses depending on the state that the queue/socket is in. This will eliminate the need for the existing state machine in the TCP stack.
The text was updated successfully, but these errors were encountered: