From 97f15b5d98a287a67b7a026dba1390d8942a9368 Mon Sep 17 00:00:00 2001 From: Michael Davidsaver Date: Wed, 17 Feb 2016 15:21:37 -0500 Subject: [PATCH] minor --- implementation.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/implementation.md b/implementation.md index 1c8bdab..e2c58fc 100644 --- a/implementation.md +++ b/implementation.md @@ -120,10 +120,9 @@ GWMonitorRequester is given a Monitor which is ChannelMonitorImpl Updates originate from the client side, entering as an argument when GWMonitorRequester::monitorEvent is called, and exiting to the server when passed as an argument of a call to ServerMonitorRequesterImpl::monitorEvent. -When called, ServerMonitorRequesterImpl::monitorEvent enqueues itself for transmission. +When an update is added to the monitor queue ServerMonitorRequesterImpl::monitorEvent is +called, as notification that the queue is not empty, which enqueues itself for transmission. The associated TCP sender thread later calls ServerMonitorRequesterImpl::send(), which calls GWMonitor::poll() to de-queue an event, which it encodes to the senders bytebuffer. It then reschedules itself. - -ServerMonitorRequesterImpl::monitorEvent is a no-op???