OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Syed Alam (Volt) (a-salamMICROSOFT.COM)
Date: Mon Jan 07 2002 - 17:59:22 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi

    In May 1999 MSJ, Don Box writes in ur column "House of COM":
     
    "Note that as long as a proxy is present, the object and client
    independently determine whether they will use blocking or non-blocking
    invocation. Also note that in the absence of a proxy, as long as the
    object supports ICallFactory as described earlier, the client can issue
    non-blocking calls directly against the object."

    In my case, the server does not support ICallFactory. If the client
    issues parallel simultaneous asynchronous calls to the COM object from
    the same thread then most of these calls fail with RPC error (even if
    separate call objects r used for each call). However parallel calls from
    different threads succeed. Can this be due to the fact that the server
    has not implemented ICallFactory interface? I earlier thought that
    client's ability to do asynchronous operations (parallel calls
    including) has nothing to do with server object's implementation
    (whether or not ICallFactory has been implemented).

    Any comments?

    Thanks

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM