OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Steve Swartz (steveswMICROSOFT.COM)
Date: Mon Jun 25 2001 - 14:16:33 CDT

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

    This is not accurate. The STA does not provide synchronization in the
    case where the component makes an outgoing call. Other calls on the
    component are accepted and processed during the outgoing call. If you
    want synchronization, you need to implement it with message filters (or
    use COM+).

    -----Original Message-----
    From: Tahsin Alam [mailto:tahsinalamYAHOO.COM]
    Sent: Monday, June 25, 2001 7:31 AM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: Single threaded DCOM server acting Multi-Threaded while
    waiting for callbacks to complete!

    From my reading of Essential COM, my understanding is
    that when an STA object makes an outgoing call and
    waits on it, its thread does return to the pool.
    However, it will only accept a callback bearing the
    same "activity id". So, if another client calls the
    STA object, that client will block. But if the object
    that the STA object called makes a return callback, it
    will be allowed in.

    This keeps the semantics of STA synchronization
    requirement while preventing deadlock situation from
    arising with callbacks to the STA object.

    tahsin

    ----------------------------------------------------------------
    Users Guide http://msdn.microsoft.com/workshop/essentials/mail.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