OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Nicholas Palmer (NICKKCICORP.COM)
Date: Mon Feb 25 2002 - 15:34:38 CST

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

    Actually Lewis, your answers were great. I was trying your first suggestion
    with the timer control when I discovered that the remote object didn't go
    away, no matter what I did or didn't do. Thanks for the answers though.

    Nick.

    -----Original Message-----
    From: Lewis Jones [mailto:Lewis.JonesONBASE.COM]
    Sent: Monday, February 25, 2002 1:21 PM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: VB Remote Server "Keep Alive" question

    Well, nuts... I was kinda proud of my answers, too...

    "VB, it's good for 90% of what you want to do, for everything else, there's
    DCOM!"

    -----Original Message-----
    From: Nicholas Palmer [mailto:NICKKCICORP.COM]
    Sent: Monday, February 25, 2002 4:17 PM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: VB Remote Server "Keep Alive" question

    You know what, you are correct. I guess I was expecting the behavior that
    occurs when using MTS/Component services were there is a timeout setting.
    For some reason I had it stuck in my head that the timeout applied to just a
    reqular DCOM ActiveX EXE components. But in testing it now, I can see that
    my remote server stays around until I exit my client app even if I do
    nothing in my client app for a while. Thanks for the answers, and sorry the
    MY confusion.

    Nick.

    -----Original Message-----
    From: Jorge A. Rodriguez Suarez [mailto:jarsRECIFE.PE.GOV.BR]
    Sent: Monday, February 25, 2002 1:34 AM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: VB Remote Server "Keep Alive" question

    There is something i don't understand...

    as far as i know, the server will keep alive the conection while he receive
    ping notification for the client, and just after this notification can't be
    received he will send notification to the client waiting for answers, and
    will try each two minutes for three times, and just after that, if the
    server don't receive notification that the client is still alive he kill the
    conection...

    am i wrong?...

    i don't understandt why your server kill the conection when the client is
    still alive and is just sleeping...

    Regards.

    ----- Original Message -----
    From: Nicholas Palmer <NICKKCICORP.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Friday, February 22, 2002 00:25
    Subject: VB Remote Server "Keep Alive" question

    > I've got a question but unfortunately, I think I know what the answer
    > will be, but here goes anyways.
    >
    > I've got a VB client app that creates an object on a remote server
    > thru DCOM. The remote object is a VB ActiveX EXE. All this is fine.
    > Now, my problem is this. If my end user on the client is doing
    > something, then
    gets
    > distracted for say 10 minutes, DCOM will have killed my object on
    > server when the user comes back, since the DCOM timeout is 6 minutes.
    > Now I
    can't
    > change the 6 minute timeout. Also, there are far to many references
    > in
    the
    > client code to the the server object to trap all of them even if I
    > could find them. So, is there anyway that I can signal the client
    > from the
    server
    > and tell it that I'm ending and have it do something. Or possibly
    > from
    the
    > client, can I "ping" the server to keep things alive, though I'm not
    > sure how I would do this in VB. Anybody run into this problem before,
    > and find away to solve it? Any suggestions would be helpful.
    >
    > Thanks in advance.
    > Nick.
    >
    > ____________________
    > Nicholas Palmer
    > KCI Computing, Inc.
    > (nickkcicorp.com)
    >
    > ----------------------------------------------------------------
    > 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

    ----------------------------------------------------------------
    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

    ----------------------------------------------------------------
    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

    ----------------------------------------------------------------
    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

    ----------------------------------------------------------------
    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