Comment #4 on issue 2620 by [email protected]: Guaranteed Ordering Of Sip Event Dispatch
http://code.google.com/p/mobicents/issues/detail?id=2620

Jean,

My opinion is that we should avoid this way.

The services beans will be there to provide logging, billing, communication,.. etc. functionality and the developer should be responsible to invoke the desired services in the order he wish. Also the communication services will always provide a final response. I think like this it will be more clear. We should leave to the container the check for the final responses.

What i suggest is to provide out of the box functionality along with a well defined programming model for the end user to follow, and that will cover 90% of the use cases. After that, we can provide the developer the choice to deviate from this by providing his own services or design but also taking responsibility of the code such as when to send the final response.

Furthermore we should provide an option to deny duplicate event observers for an application and have it enabled by default. The developer who wishes to deviate would be able to disable this option.

George

Reply via email to