Hi Elias,
you specify a callback via a function pointer - the code of the function
exists in all processes (fork duplicated the code). So, the callback
functions are executed by the process which process the requests that
triggers the callback.
the processing of the the requests/replys is very serial....
regards,
bogdan
Elias Baixas wrote:
Hi all, I have a question regarding transaction module callbacks:
when I register a callback with register_tmcb( struct sip_msg* p_msg,
struct cell *t, int types, transaction_cb f, void *param ), the
transaction_cb function will be a pointer to a function in the address
space in the process which is registering the callback, so whenever an
event triggering the callback happens, the function which will be
called will always be in the same process address space, so the
callback must be very-reentrant, because that process may already be
processing a request/response.
Am I right ? what issues should I take very care of while executing
the callback ?
I'm doing my final project in telecommunications engineering. I'm
coding a SER module to generate transactions in behalf of external
events that will be reported to my module.
Thanks for your help !
Elias
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
