Re: [reSIProcate] [reSIProcate-commit] resiprocate 7042 nash: DialogUsageManager:

["Derek MacDonald" <derek@xxxxxxxxxxxxxxx>]

Hi Nash, 

What is the motivation for InviteSessionHandler::AnswerReason? This adds complexity and doesn't really fit the DUM api, and will complicate PRACK development, or separating out the offer/answer state machine. I think we should remove this unless there is a compelling use case.

-Derek

On 4/9/07, svn@xxxxxxxxxxxxxxx <svn@xxxxxxxxxxxxxxx > wrote:

Project	resiprocate
New Revision	7042
Committer	nash (Nash Tsai)
Date	2007-04-09 02:02:41 -0500 (Mon, 09 Apr 2007)

Log

 DialogUsageManager:
  add ExternalMessageHandler interface
  add hasEvent method
  changes to process methods to allow mutex lock while in-processing
 
 ClientRegistration/ClientSubscription/ClientPagerMessage/ClientPublication/InviteSession/ServerInviteSession/ServerPagerMessage:



  Provide asynchronous method access by using command
 
 

Added:

• main/resip/dum/ExternalMessageBase.hxx
• main/resip/dum/ExternalMessageHandler.hxx

Modified:

main/resip/dum/ClientInviteSession.cxx
main/resip/dum/ClientInviteSession.hxx
main/resip/dum/ClientPagerMessage.cxx
main/resip/dum/ClientPagerMessage.hxx
main/resip/dum/ClientPublication.cxx
main/resip/dum/ClientPublication.hxx
main/resip/dum/ClientRegistration.cxx
main/resip/dum/ClientRegistration.hxx
main/resip/dum/ClientSubscription.cxx
main/resip/dum/ClientSubscription.hxx
main/resip/dum/DialogUsageManager.cxx
main/resip/dum/DialogUsageManager.hxx
main/resip/dum/DumCommand.hxx
main/resip/dum/InviteSession.cxx
main/resip/dum/InviteSession.hxx
main/resip/dum/InviteSessionHandler.cxx
main/resip/dum/InviteSessionHandler.hxx
main/resip/dum/ServerInviteSession.cxx
main/resip/dum/ServerInviteSession.hxx
main/resip/dum/ServerPagerMessage.cxx
main/resip/dum/ServerPagerMessage.hxx

_______________________________________________
resiprocate-commit mailing list
resiprocate-commit@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-commit