Connection Binding

A client connection can be bound to a single worker process. Events for a bound connection are directed to that bound worker. Events for unbound connections are handled by any worker.

Events for bound connections have higher priority than those of unbound connections.

A connection can be bound and unbound multiple times. A connection can be:

• Bound to the current process

• Bound to a worker identifier (the current or another worker process)

• Unbound from the current process

For unbound events, the most-recently idle worker is always the first woken.

If a worker process terminates holding bound connections, those connections are closed.