yumapro  24.10-1
YumaPro SDK
Loading...
Searching...
No Matches

extra information not used very often within a val_value_t More...

#include <val.h>

Collaboration diagram for val_extra_t:

Data Fields

xmlChar * dname
 malloced value name used rarely if obj_get_name not correct this can happen if val_value_t trees are constructed by SIL code from generic objects; This is NOT RECOMMENDED Use val_init_from_template using correct obj_template_t instead More...
 
void * getcb
 Used by Agent only: GET1 callback for virtualval if this field is non-NULL, then the entire value node is actually a placeholder for a dynamic read-only object and all read access is done via this callback function; the real data type is getcb_fn_t *.
 
struct val_value_t_ * virtualval
 if this field is non-NULL, then a malloced value struct representing the real value retrieved by val_get_virtual_value, is cached here for <get>/<get-config>
 
time_t cachetime
 timestamp for virtual val timeout
 
struct xpath_pcb_t_ * xpathpcb
 this field is for NCX_BT_LEAFREF NCX_BT_INSTANCE_ID, or tagged ncx:xpath value stored in v union as a string
 
plock_cb_tplock [VAL_MAX_PLOCKS]
 back-ptr to the partial locks that are held against this node
 
dlq_hdr_t * dataruleQ
 back-ptr to the data access control rules that reference this node More...
 
xmlChar * varexpr
 malloced pointer to the variable expression found if this val node is part of a data template. More...
 
struct xpath_aio_cb_t_ * aiocb
 Used by xpath_aio.c and agt_xpath.c to keep track of the parent of a top AIO val_value_ tree. More...
 
ncx_sm_mpid_tmpid
 malloced Moint Point ID struct if found in parsing
 

Detailed Description

extra information not used very often within a val_value_t

Field Documentation

◆ aiocb

struct xpath_aio_cb_t_* aiocb

Used by xpath_aio.c and agt_xpath.c to keep track of the parent of a top AIO val_value_ tree.

This is a backptr.

◆ dataruleQ

dlq_hdr_t* dataruleQ

back-ptr to the data access control rules that reference this node

Q of obj_xpath_ptr_t

◆ dname

xmlChar* dname

malloced value name used rarely if obj_get_name not correct this can happen if val_value_t trees are constructed by SIL code from generic objects; This is NOT RECOMMENDED Use val_init_from_template using correct obj_template_t instead

malloced name if needed

◆ varexpr

xmlChar* varexpr

malloced pointer to the variable expression found if this val node is part of a data template.

The actual value in union v_ MUST be ignored if varexpr string is non-NULL!!


The documentation for this struct was generated from the following file: