[Common-dev] Re: [Protocol-dev] CR: Fix socket event handling

[Common-dev] Re: [Protocol-dev] CR: Fix socket event handling

Tom Marshall tmarshall at helixcommunity.org
Thu Oct 21 15:01:43 PDT 2004


On 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


More information about the Protocol-dev mailing list
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.