[Devel] exporting pseudo variables
Daniel-Constantin Mierla
daniel at voice-system.ro
Tue May 2 12:46:53 CEST 2006
On 05/02/2006 01:33 PM, Klaus Darilion wrote:
> Are pseudo variables allowed to overlap? e.g.
>
> $tls_cipher and $tls_cipher_bits ?
yes, the name goes until an invalid characters for names is found. Valid
characters for names:
0-9
a-zA-Z
. (dot) _ (underline)
If you need to mark the name use $(name). For example:
$(tls_cipher)_bits will print $tls_cipher followed by "_bits".
Cheers,
Daniel
>
> thanks
> klaus
>
>
> Daniel-Constantin Mierla wrote:
>> Hello Klaus,
>>
>> On 05/02/2006 01:03 PM, Klaus Darilion wrote:
>>> Hi Daniel!
>>>
>>> Is it possible to do the parsing of the pseudo variable in the
>>> module? E.g. for tls there will be similar paramters, for the peer
>>> certificate and the local certificate. Is it possible to register
>>> only a prefix, e.g. $tls_ and parse the latter in the module itself?
>> no, the parsing is done by core. The modules can add new specifiers,
>> but must be the full name, so they are visible in other modules as
>> well.. You can add many specifiers with the same callback function
>> and different values of the parameter.
>>
>> Cheers,
>> Daniel
>>
>>>
>>>
>>> regards
>>> klaus
>>>
>>>
>>> Daniel-Constantin Mierla wrote:
>>>> Hello,
>>>>
>>>> On 04/28/2006 12:05 PM, Klaus Darilion wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> I'm studying how to export pseudo variables.
>>>>>
>>>>> In tm.c there is this code:
>>>>>
>>>>> if(xl_add_extra("T_branch_idx", it_get_tm_branch_idx, 100
>>>>> )!=0)
>>>>> {
>>>>> LOG(L_ERR,"ERROR:tm:mod_init: failed to register
>>>>> pvar "
>>>>> "[T_branch_idx]\n");
>>>>> return -1;
>>>>> }
>>>>>
>>>>> Thus I guess the exported pseudo variable is called $T_branch_idx,
>>>>> but the README says:
>>>>>
>>>>> $T_branch_index - the index (starting with 1 for the first branch)...
>>>>> ^^^^
>>>>>
>>>>> Is guess there is a typo.
>>>>
>>>> indeed.
>>>>
>>>>>
>>>>> Further, do we have a schema how to name the exported pseudo
>>>>> variables?
>>>>
>>>> There is none, but the name should be suggestive as much as
>>>> possible. Somehow, we should find one to avoid duplicates.
>>>>
>>>> Cheers,
>>>> Daniel
>>>>
>>>>>
>>>>> regards
>>>>> klaus
>>>>>
>>>>> _______________________________________________
>>>>> Devel mailing list
>>>>> Devel at openser.org
>>>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>>>
>>>
>>>
>
>
More information about the Devel
mailing list