-> How we can cache the properties?
-> How the cache properties can be updated?
This POC is to get a feed back on the caching approach?
Are we on right direction or should we change the
direction?
Create the Dbusinterface class which is the interface
class to invoke the Dbus opertiaon, The idea is to
create the new function in the class for the opertaion like
GetMangedObjects,GetSubtreepaths. which internaly creates the
match object(properties changed) for all the managed objects
or under the given root and ceates the match for interface added/
interface removed.
Once match gets hit the call back is called(notiFy handler) for the
object.
-Create the data interface class which is to keep all the raw data
for the logentry(Bmcdump, SystemDump).
Data interface class uses the DbusInterface class for getting all the
manageed objects.
Callback gets called when there is any update on the Dbus object to update the
cached properties
-> Interface added/ removed/ Properties changed.
What needs to be done->
Update the map in the DbusInterface class when there is a user initiated
delete action.
certian code is commented which needs to be corrected.
The aim was to get the feedback about the approach.
-> How we can cache the properties? -> How the cache properties can be updated?
This POC is to get a feed back on the caching approach?
Are we on right direction or should we change the direction?
Once match gets hit the call back is called(notiFy handler) for the object.
-Create the data interface class which is to keep all the raw data for the logentry(Bmcdump, SystemDump).
Data interface class uses the DbusInterface class for getting all the manageed objects.
Callback gets called when there is any update on the Dbus object to update the cached properties -> Interface added/ removed/ Properties changed.
What needs to be done->
The aim was to get the feedback about the approach.
Signed-off-by: Ratan Gupta ratagupt@linux.vnet.ibm.com