Re: AttributeStore and Listeners.
- From: Tom Strickland <
- To: "
- Subject: Re: AttributeStore and Listeners.
- Date: Tue, 5 Nov 2013 11:34:08 +0000
After chatting about this briefly with Keith...
This seems like an attractive idea, but don't we lose the generic-type
information at runtime? If so, how will the container tell that a class
implementing AttributeStoreListener<SipSession> is interested in
On 5 November 2013 09:43, binod pg
> Hi everyone,
> At the moment, for SipSession and SipApplicationSession, there are two
> sets of attribute listeners
> With the new AttributeStores like ForkingContext (SipCall), we probably
> have more of these listeners.
> Would the following more generic listeners make sense instead?
> AttributeStoreBindingEvent<T extends AttributeStore>,
> AttributeStoreBindlingListener<T extends AttributeStore>,
> AttributeStoreListener<T extends AttributeStore>,
> And deprecate the specific listeners for SipSession and SAS?
Note: The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it
from your computer. Thank you. CafeX Communications.