EPICS_base/pva2pva
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

minor

Browse Source
This commit is contained in:
Michael Davidsaver
2016-02-17 15:21:37 -05:00
parent e35f06cb00
commit 97f15b5d98
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
implementation.md
View File

@ -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???