Hi all.
Designing a new TransactionObserver interface and it struck me that we already
have half of a formal plug-in API in the set of *Observer interfaces. They
nicely define all the call-out points from the broker to plug-ins.
The other half is the set of broker library functions called by plug-ins. This
could be formalized but needs a bit of research to find out just what broker
functions are being used and to organize them in sensible classes. E.g. there
might be a restricted interface to broker::Queue provided to plugins etc.
I've got no immediate plans to do this but thought I'd float the idea in case
anyone is interested or has better ideas about how to design a plug-in API.
Cheers,
Alan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
