[omniNotify] Mapping Filters and Persistence

[Robert E. Gruber]

I do not plan to implement persistence any time soon, but perhaps
someone else might be interested.

This would not be a trivial project.  If someone wanted to work on it,
I would be willing to support that effort by answering questions and
helping to resolve issues as they come up.

Mapping filters: I believe they only map certain values,
timeout and priority, neither of which would work
as a 'supplied from' field.
I think there is an OMG spec on managing networks of
event channels.  omniNotify does not support it, but you might at least
look at it and check which notification services do support it.

-- Bob


On Thu, 13 Feb 2003, Cameron Rochester wrote:

> Hi,
>
> I am currently investigating Notification Services and have a few questions
> about omniNotify.
>
> 1) I realise that persistence (EventReliability or ConnectionReliability) is
> not supported currently. Is there any work being done in this area at the
> moment? Do you have any idea how much effort would be involved in
> implementing this?
>
> 2) Are mapping filters supported?
>
> My question about mapping filters arises from our need to federate
> Notificatio Services. The main problem we foresee is Event 'feedback' where
> you have a Notification Service both supplying and consuming events from
> another Nofitication service. One option would be to use a 'hop count', or
> 'supplied from' field in the filterable data that can be used to prevent
> 'feedback'. I think this may be achievable using mapping filters but I am
> not entirely sure. Does anyone have any suggested solutions to the problem -
> or point me in the direction of some info that could help.
>
> Regards
> Cameron Rochester
>
> Software Engineer
> Ripple Systems Pty Ltd
> Ph: +61 893688616
> Fax: +61 893688699
> _______________________________________________
> omninotify-list mailing list
> omninotify-list@omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omninotify-list
>