Hi,
To make this thread get more visible attention, I changed the subject name
to one small feature request to implement event/state mask, also copied
Pekka to address this request.
Frankly speaking, I don't have overhead statistics of those extra event
reported to application layer. But as we know,
according to Sofia's architecture implment philosophy, every ( almost? )
event and state change signal associated with callback funtion is at first
inserted and queued into a internal list whose element will be popped and
executed asynchronously. I don't get those function profiling data, but
let's roughly image, we have overhead of callback function invoke, internal
event/signal queuing/popping. It maybe trivial overhead compared to whole
application logic processing, but let's say if our system is fully loaded
with huge call volume. Those little overhead could accumulates to a certain
level which we can definitely save to our real application logic. Why not ?
:-)
So my humble proposal is that we implement bitwise event/signal mask just
like pthread_signal_mask provided by most posix thread library. With that
let's say, for example, application programmer masks certain event/signal
which he is not interested. When those events are triggered, we don't need
insert to sofia internal queue any more.
Mikhail,
For the CANCEL question, I tried APPL_METHOD before I writed mail to
mail list, but failed. I think, stack code change is needed.
Thanks
kandy
2008/10/28 [EMAIL PROTECTED]
Hi,
--
*From:* ext liu yang [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, October 28, 2008 10:49 AM
*To:* sofia-sip-devel@lists.sourceforge.net
*Subject:* [Sofia-sip-devel] disable automatically 200OK response to
incomingCANCEL
Hi all,
Actually I have two question here.
First one is the one explained in mail subject. In detail, we know, sofia
stack automatically responds with 200OK for incoming CANCEL.
My purpose is just to add an special customized SIP header into this 200OK.
By checking related code, I didn't find any clue to achieve this.
So without modifying stack code, is there any simple way, like including a
TAG somewhere to meet my requirement?
Try to list CANCEL in NUTAG_APPL_METHOD string.
Second one is more specific to sofia fundamental framework, which is I
expect to prevent some event/signal from being reported to application.
The mechanism is just like, we unmask certain OS signal using
'pthread_signal_mask'. With this methodology, sofia stack only sends event
which application
layer is interested upwards to save both a bit cpu usage of upper
application and sofia stack.
How much CPU usage you're aiming to save, is it anywhere comparable with,
say, media processing?
There are no filters or masks for events AFAIK, but I don't see much use
for them.
Best regards,
Mikhail
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
