3 Feb
2009
3 Feb
'09
12:46 p.m.
Hello everyone,
and thank you for your welcome !
2009/2/3 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
code will be unfrozen in few weeks. As personal preference, returning code
is a more flexible way, as the config writer can chose what to send.
Changing the return code for a function is not a new feature IMO. However,
I mean by that to do it with the current design. If I am not wrong there is
a pipe communication between sip worker processes and purple worker
processes.
Yes you're right, purple has it's own process.
You cannot get the error in purple processes and
return it in the sip
process. What you can do is to have a different reply code if you had an
error while building the packet for purple process (e.g., no more memory)
and once you send it to purple process return true and the code writer
should reply with 202 Message accepted.
My problem is that I currently don't know how to return synchronously a
reply code from the pipe's other side.
Can I use the pipe to write back from the purple process to the "main"
process ?
Cheers,
Daniel