Comment #3 on issue 2620 by jean.deruelle: Guaranteed Ordering Of Sip Event
Dispatch
http://code.google.com/p/mobicents/issues/detail?id=2620
Georges,
Sorry for not updating the issue, but I had an offline chat with thomas
yesterday and asked him to create this issue.
This is about dispatching the event within an application to multiple
servlets.
By example, if you have within the same application, 3 different components
watching for @Observes @Invite SipServletRequest req
Component A is listening for INVITE with priority 1, it gets the invite and
just log it
Component B is listening for INVITE with priority 2 and check billing
Component 3 is called with priority 3 and send back a final response then
no other components of the same application can be called.
The last one is a mandatory feature to make sure that if a servlet has
already sent a final response then no other servlets can get the request
Ideally the priority could be configurable through an external mechanism so
that if you compose components from third party libraries you can modify
the priority depending of the ordering you want.
This would foster modularization and decomposition in multiple components
for the sip application developper.
Feel free to comment
Jean
