Hi list, I've got something working in OpenOCF that might fit with Iotivity. The idea is that, at least for debugging, we can database messages. On the client side we add a KEEP_MESSAGE flag to complement the KEEP_TRANSACTION flag. There is no reason a client should need to copy the response msg; it has already been allocated. So the client handler calls a register fn to save the pointer and then returns KEEP_MESSAGE. Client is responsible for freeing.
To complement this we have a client API, e.g. get_resources returns the list of resources that were saved by the register fn. Or more generally this would be a client-side API for "coresources" corresponding to the server-side resource API. Motivation: I'm working on an OCF browser based on ncurses ( https://github.com/OpenOCF/iochibity/tree/master/examples/browser). So I need to save the results of a discovery in order to present them to the user. The logic involved could be supported by the engine, so the user does not have to deal with it. Waddyathink? g
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
