Know problems or restrictions with SocketPro

        At this time, SocketPro has gradually become matured with MS Window operation systems. However, It does not mean that we'll stop innovating it. Contrarily, we are still improving it with adding more services into SocketPro package. We are looking forward to your feedback and questions. If you find a problem, please report it to us. We'll fix it at as early as possible. 

        Currently, there are a few know minor problems or restrictions with SocketPro. Most of them are related with MS CE and smart phone.

.NET button control focus problem:

1. When calling the method Wait, WaitAll or ProcessRy inside button events function at client side, the button focus does not work correctly in some cases. You can use any one of the below three methods to solve this problem.
   a.    Don't use the method Wait, WaitAll or ProcessRy. You can use the async methods instead to solve the problem.
   b.    Call the method Focus to set the focus onto its parent window before calling the method Wait, WaitAll or ProcessRy.
   c.    Don't let too many Wait, WaitAll and ProceesRy queued. For example, disable controls until previous Wait, WaitAll or ProceesRy method returns.

MS CE and Smartphone:

1. SocketProAdapter for compact .NET 2 does not support serializing/de-serializing objects with binary or soap format, because MS compact .NET 2 has no binary or soap serialization support on device platforms. If you try to use the method CUQueue::Serialize or Deserialize, you will get an exception. However, you can use methods XmlSerialize or XmlDesrialize instead.
2. The class CUQueue in SocketProAdapter for .NET 2 does not support packing or unpacking a FILETIME structure. 
3. SocketProAdapter supports MS compact .NET 2 or later only.
4. The dll usocket.dll for devices doesn't support the method IUCert::Verify to verify server certificate chains through MS SSPI channel, because MS device platforms don't have API function CertVerifyCertificateChainPolicy available.
5. SocketProAdapter for compact .NET 2 has no generics CSocketPool, but we may add it in the future if generics CSocketPool is needed.

Win 95, 98 and ME:

1. By default, MS SSPI is not enabled with the three platforms. To enable it, use Regedit.exe to change the following registry key value: 
           
   Start Registry Editor (Regedit.exe).
   Locate the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders 
   
   On the Edit menu, click Modify, and then modify the following registry value:
   Value Name: SecurityProviders
   Data Type: REG_SZ
   Value: Append ",schannel.dll" (with comma, no quotes) to previous string. 

OpenSSL:

1. You can not call the method ISocketBase::Disconnect inside the function OnSocketConnected at client side if you use OpenSSL to secure socket data communication. Doing so will crash a client application.

Big-endian and little-endian:

1. Anything related to big-endian or little-endian is not implemented.

 64bit Mozilla browsers

1. Because there is no 64-bit mozilla browsers available on window platforms. At this time, there is no 64bit npUSocket.dll available for Mozilla-based browsers. When ready, we will update it for support on 64bit Mozilla browsers in the future.