Hi,

On Wed, May 15, 2002 at 08:12:29PM +0530, K S Sreeram wrote:
> > When relying on WRITE events using the ACE_WFMO_Reactor, you must
> > therefore continue to write until the connection closes or the socket
> > becomes flow controlled, i.e., a send fails with EWOULDBLOCK.
>
> if ( write() == EWOULDBLOCK ) then {
> ...
> . ...
> ...
> wmfo_reactor->handle_events()
> }
>
> what happens when the socket transitions from flow-controlled to writeable
> after the call to write but before the call to handle_events()? If WFMO, is
> not going to notify the caller about the transition, then using WFMO_Reactor
> for socket write notification would not be reliable, and hence should never
> be used...

The event hasn't been reported yet so presumably the WFMO reactor will
still report the event. If not, then Windows'
WaitForMultipleObjects() call bites. ;-)


-Ossama
--
Ossama Othman <ossama@...>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8