Hello,
some months ago (iirc) we had a discussion about the sip_msg structure
and the fact that it has too many header hooks, some for pretty uncommon
or not really used inside sip router code.
I spotted
- subject
- accept_language
- content_disposition
- accept_disposition
- unsupported
- organization
- diversion (expired draft?)
The list can continue a bit ... I was thinking to replace them with a
call of get_hdr_by_name|type() kind of function. The benefit will be
lower structure.
On the other hand, I would add a new field to hold the pid of the
process that received the message. There are some potential races by
using only id to identify a message, especially in serial forking.
Opinions?
Daniel
--
Daniel-Constantin Mierla
eLearning class for Kamailio 3.0.0
Starting Feb 8, 2010
* http://www.asipto.com/
Revision: 5979
http://openser.svn.sourceforge.net/openser/?rev=5979&view=rev
Author: miconda
Date: 2010-02-02 21:31:30 +0000 (Tue, 02 Feb 2010)
Log Message:
-----------
Tagging the 1.4.5 release
Added Paths:
-----------
tags/1.4.5/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5978
http://openser.svn.sourceforge.net/openser/?rev=5978&view=rev
Author: miconda
Date: 2010-02-02 21:30:47 +0000 (Tue, 02 Feb 2010)
Log Message:
-----------
Tagging the 1.5.4 release
Added Paths:
-----------
tags/1.5.4/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.