| [ecf-dev] RFC 119 Modified-endmatch support |
Hi all,
Should the OSGi event MODIFIED-ENDMATCH be part of ECF 3.0?
The basic idea behind this event is: a consumer (listener) gets notified if a provider has changed the properties of its publication in a way, that the published resource (a service) is still available, but the filter of the consumer (listener) does no longer match this published service. The consumer gets then notified about that change by MODIFIED-ENDMATCH.
SEN starts working on that topic.
Everyone is welcome to share their thoughts. Help is appreciated.
We will open a bug for that, depending on the outcome of this discussion.
Mit freundlichen Grüßen / With best regards
Thomas Kießlich
Siemens Enterprise Communications GmbH & Co. KG
HiPath Applications
SEN LIP DA 11
Schertlinstr. 8
81379 Munich, Germany
Phone: +49 (89) 722-32483
Fax: +49 (89) 722-40560
Email: thomas.kiesslich@xxxxxxxxxxx
Communication for the open minded
www.siemens.de/open
www.siemens.com/open
Siemens Enterprise Communications GmbH & Co. KG; Registered office: Munich; Commercial registry: Munich, HRA 88546; WEEE-Reg.Nr. DE 27980375; General Partner: Siemens Enterprise Communications Management GmbH; Managing Directors: James R. O’Neill, Stephen Jones, Todd Schorr; Registered office: Munich; Commercial registry: Munich, HRB 163415
Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG
Important notice: This e-mail and any attachment thereof contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you.