FIG. 5 is a flowchart according to another embodiment for generating a gossip message. In process block 510, a request is received from a client computer to establish a communication session. For example, in FIG. 2, a client computer 102 can request a communication session with host computer 289. As a result of the request, a socket can be opened on the host server computer 289. In process block 520, the host server computer can accept the request and store an event in a shared maps memory that a communication session has been established. For example, in FIG. 3, once a socket is opened, the L4 LB socket operations 340 can store the event in the shared maps 342 for consumption by the user space 266. In process block 530, the user space application detects the event and transmits a gossip message to the other host server computers in the POP. The gossip message includes a confirmation that a communication session has been established. For example, in FIG. 3, the user space L4 LB 350 can read the event from the shared maps 342 and transmit a gossip message to all hosts found in the active hosts storage 354. In process block 540, when the communication session closes, another event is stored in the shared maps. For example, in FIG. 3, the L4 LB socket operations 340 can store the socket closure event in the shared maps 342. In process block 550, the user space L4 LB application 350 detects the event and transmits another gossip message to the other host server computers in the POP that the communication session has been closed. For example, in FIG. 3, the user space application 350 can transmit the gossip message indicating that the socket has been closed to all hosts listed in the active host memory 354.