[Users] Persistently storing headers from onreply_route()?

[Bogdan-Andrei Iancu]

Hi Joachim,

apply the attached tm.patch - it's trivial change that will synchronize 
the execution of on_reply route. And it will be safe to use avpops 
functions in on_reply routes. Note that you have to change the module 
interface of AVPOPS and add the ONREPLY_ROUTE flag.

regards,
bogdan

PS: if you get a coredump, I'm free of any responsibilities :D

Joachim Fabini wrote:

>Hi Bogdan,
>
>  
>
>>the reason haven't changed: avps doesn't work in on_reply route since 
>>the avp belong to a transaction and the on_reply route 
>>execution is not synchronized and may be done in parallel for same 
>>transaction.
>>
>>For the moment there is no solution to this - synchronizing 
>>the on_reply routes will be quite ugly :-/
>>    
>>
>
>Do you see another - even proprietary - very-short-term-workaround 
>that can provide this functionality (storing avps within onreply_route
>in the database that can be later on accessed from the route block 
>using avp-ops) without extra module coding? 
>Ugly is not important at all if it works. After all it's just about 
>prototyping, the final code should be clean... ;))
>
>  
>
>>But what will be done (there was a discussion with Juha on 
>>this topic) is to add global avps which not being bound to 
>>a transaction can be used inside on_reply route. I guess this 
>>will solve your problem....
>>    
>>
>
>Definitely. That's also conceptually closer to what Service-Route
>is supposed to do - it's valid for the lifetime of a registration
>(although it might be changed by re-registrations) and not just
>for one transaction. Any estimate when this will be available?
>
>Thanks for your help,
>regards
>--Joachim
>
>
>  
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tm.patch
Url: http://lists.kamailio.org/pipermail/users/attachments/20051019/fda8318b/attachment.txt