[omniORB] Re: [omniNotify] Object Gargabe Collector
Bob Gruber
bob.gruber at gmail.com
Fri Aug 6 10:30:01 BST 2004
I'm afraid that notifd does not currently inform clients (via a
disconnect_foo call) when an otherwise valid proxy is discarded due to
GC. That needs to be fixed, but I do not have time to do any fixes
this month. I will definetely get it done in September.
Until then, your other strategy described below would work. You could
also set the DeadCon GC to a huge value -- 2 days, or whatever
(something much larger than any correct client will ever go).
-- Bob
----- Original Message -----
From: Frederic Prin <frederic.prin at silvaco.com>
Date: Fri, 6 Aug 2004 14:52:27 +0200
Subject: [omniNotify] Object Gargabe Collector
To: omninotify-list at omniorb-support.com
Cc: omniorb-list at omniorb-support.com
Hi,
I use "DeadConProxyInterval 600" to garbage my unsused Connected Proxy.
It works well but it's hard (or impossible) to fine tune the value...
I was wondering if a consumer app (push structured style) is notified
when notifd is going to garbage a still connected but unsused proxy
(since 600s) object ?
If not I will set DeadConProxyInterval to 0 with
DeadOtherProxyInterval to 600.
Thanks
FredP
(
Frédéric Prin )
Senior Software Engineer /
S I L V A C O (
Grenoble REsearch CEnter \
Tel 04 56 38 10 33 )
__________________________/___
/__/__/__/__/__/__/__/__/__/__/
/__/__/__/__/__/__/__/__/_____/
/__/__/__/__/__/__/__/__/__/__/
More information about the omniORB-list
mailing list