From: Jan M. <jpm...@gm...> - 2008-04-23 17:00:02
|
Tito Garrido schrieb: > Sorry, I didn't understand what you're trying to do... Could you explain? i'm basically streamlining and extending the Manager class for myself, just wondered if anybody else is interested. 1. i fixed some minor bugs in the Manager class concerning (un)registering events (see my former post) 2. i wrote a "one-fits-all" method for the Manager class which takes a table (which is a manually edited cut-and-paste of the API command help) as input and generates methods like manager.ping(), manager.db_put(family, key, value), ... for _all_ simple manager actions (which have just a simple response w/o events). i just don't have a zap module running, so i didn't implement the "Zap*" actions. anyway, i would really prefer an external machine-readable table containing all API commands, their parameters, and their documentation string, which is kept up-to-date by someone. Probably a wiki author or even the asterisk developers might be interested as well in a unified api command table. 3. i implemented methods sip_peers and db_get which register for the query result events, then unregister again and return a list of Event objects containing the data which was asked for. as already said, it's all pretty alpha, but very useful for me, and i'll go on developing it for my needs. i passed it to stephen for a test drive. regards j. |