[Common-dev] Re: [Protocol-dev] CR: Fix socket event handling
Tom Marshall tmarshall at helixcommunity.orgOn Thu, Oct 21, 2004 at 02:34:47PM -0700, Liam Murray wrote:
> Do you need to handle the dualsocket case in SelectEvents?
>
> STDMETHODIMP
> CHXSocket::SelectEvents(UINT32 uEventMask)
> {
> +#if defined(MISSING_DUALSOCKET)
> + if (m_pSock4)
> + {
> + m_pSock4->SelectEvents(uEventMask);
> + }
> +#endif
Yes, good catch. That was previously in the derived SelectEvents.
> I was able to get this to work on the client by implementing Select() in
> the derived class. It appears to work fine once I do that.
Cool. So it looks like this is okay from the client perspective?
I'll send out a final CR in a bit. Thanks for testing this.
--
The only thing more costly than stretching the schedule of an established
project is accelerating it, which is itself the most costly action known to
man.
-- Norman Augustine
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.helixcommunity.org/pipermail/protocol-dev/attachments/20041021/94b0b35d/attachment.bin