GDPR, 2018: Please see the revised Pivacy Policy for this wiki: General Data Protection Regulation
Please Note: You must be logged in to edit this wiki and your account must be assigned "editor" rights (set by administrator).
A function, described for an interface, that is passed as an argument (reference) from a host to a client that is expected to be used at a given time to handle a client request for service from the host. A STAM Callback is considered a synchronous callback as it blocks waiting for the request to be fulfilled.
A client has specific interface operations that must be supported (may only have read-only requirements) that are published in the description of the client for its interface (e.g., I2CWrite(addr, value), I2CRead(addr) – It might be simplified as setaddr(addr), write(value), read() to make it more abstract?). The host registers its handler for that client with the client as a callback reference. The registration must be described by STAM directives to provide the mapping of the model. The key is the interface must have an agreed upon set of callbacks that may be available. If a required callback is not registered, the client may have some alternate method of using other callbacks in concert to fabricate the desired behavior. That case is of course rare.