Home
[RDK Central Wiki]
CMF
[Code Releases]
I noticed that there some definitions named COSA_XML_type_dynamicTable, COSA_XML_type_writableTabl and COSA_XML_type_dynWritableTable, it related the data model xml file defined the object type named
dynamicTable, writableTable,dynWritableTable.
I want to know what's difference about the code handling on these three types? and each type is used to which scenario?
Thank you!
4 Comments
sipra samantray
Hi Tang Heming ,
The total number of entries in the table may be a static number or may grow / shrink dynamically. The table object with fixed number of table entries is called as static table and table object whose table entries grows / shrinks dynamically is called as dynamic table.
The table object that allows other components (consumers) to add entries in its table is called as "dynamic writable table"
Thank you.
Tang Heming
sipra samantray Hello, thank you!
I understood what you said above.
When to use 'writable table'? and when to use 'dynamic writable table'? Could you provide some scenarios for examples?
if we have a dynamical table and can be add/delete the table entrance from ACS side? which one should be used?
if we have a dynamical table and can not be add/delete the table entrance from ACS side, but the parameters of the table can be modified from ACS side, which one should be used?
if we have a dynamical table, which can be add/delete the table entrance from other components inside the CPE, but can not be add/delete from ACS side, which one should be used?
if we have a static table and the parameters can be modified from ACS side, which one should be used?
sipra samantray
Hi,
Usually all tables are associated with MaxInstance that it can have index.
For all table you can add a new instance from ACS. What it does after that is based on what type of table it is.
For example :
writableTable - Consider IP.Interface which is predefined usually for any OEM, we don't need this to grow during run time, so this is static table.
dynamicTable - AssociatedDevice table in Wifi, here the instance can grow at run time based on client connect/disconnect, but don't really need to synchronise the table at runtime.
dynWritableTable - PortMapping table, it can grow at anytime, even user can add new entry from UI. Anytime a new entry added/removed by another component or PA, this table needs to be synchronized at run time to manage the index. Here basically we need synchronization of table at run time.
Tang Heming
Hi sipra samantray
Thank you very much this useful information.
One more question about your explanation.
"dynamicTable - AssociatedDevice table in Wifi, here the instance can grow at run time based on client connect/disconnect, but don't really need to synchronise the table at runtime."
here 'synchronise', what's that meaning from source code logic view?