[omniNotify] omniNotify cfg file (QoS values)

[Janet Tvedt]

On Wed, 2004-06-02 at 01:50, Frederic Prin wrote:
> Hi all,
> 
> Is there someone that uses the omniNotify (notifd) Notification Service
> ? 
> 
> I'm trying to fine tune the cfg file regarding the notifd memory usage
> and I need some help!
> 
> Is anybody knows the maximum values for these QoS:
> 	QueueGCPeriod		30
> And
> 	ObjectGCPeriod            600
> 	DeadChanInterval            0
> 	DeadAdminInterval           0
> 	DeadConProxyInterval        0
> 	DeadOtherProxyInterval    600
> 	DeadFilterInterval          0
> 
> 
> 
> 
> Is nobody has the answer, I will really appreciate a global opinion on
> omniNotify.
> (In particular the notifd daemon.)
> Or if you don't use omniNotify, what kind of asynchronous event
> messaging features do you use instead ?
> (omniEvents for example or something of your own)
> 
> Thanks in advance
> 
> Fred
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> omninotify-list mailing list
> omninotify-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omninotify-list

Fred,

I have been using notifd for several years now and am quite pleased with
the performance.  Initially we had problems with memory growth and
occasional lockups.  Bob Gruber fixed those problems.

I am not using the latest version however since I don't recall the
Deadxxx QoS parameters.  I assume that these specify when notifd should
perform some sort of cleanup operation.  I would use the default values
unless you have a good reason to change them.

Several years ago I tried using several event services including
omniEvents.  None were adequate for my application.  The primary problem
I had was with scalability.  omniNotify was the first notification
service I evaluated.  It works for us so I have not had a need to
investigate others.

Hope this helps a little.

-- 
Janet Tvedt
National Solar Observatory
Tucson, Arizona