Re: [Pyst-users] functions for database access

[Matthew N. <mni...@di...>]

Jan Müller wrote:
> Matt,
> 
> thanks for your feedback. Like I've said, just quick and dirty. At least
> to my knowledge (searching the web for a day), so far, there are close
> to zero examples for the usage of pyst, so I meant to contribute a
> "how-to find back an event associated to an action" (identified by an
> action_id), and my next step would indeed have been to implement my own
> Action class with, e.g., a method events().
> 
> The very same structure, as far as I can deduce from a glimpse on astxx,
> is one of the main improvements in the class hierarchy (taken aside the
> more robust reduction of threads), so this looks quite promising, and I
> guess I prefer to live with my self-knitted solution as is, until you do
> better. Anyway, I would like to contribute to the testing, if you are
> interested and I find the time.

Ok, keep an eye on the mailing list for information on pyst 0.3, I can 
tell you now that there are no immediate plans to develop it, but I will 
work on it when I have some time and/or I have a pressing need for it.

> I share your opinion about the importance of a versatile and robust
> low-level functionality, nevertheless I think there should be a medium
> level module, too, which reflects the spectrum of Manager actions,
> including also database functions. For example, I don't get what makes
> mailbox_count or setvar, say, (and even originate) more low-level than
> database access?

Glad to see you understand my point of view.  I agree that there is a 
place for higher level functionality, but I don't think that should be 
included in the core functionality.  Maybe there should be a pyst-aux 
lib or something.

As far as mailbox_count and setvar, these manager actions are not 
defined in manager.c of the asterisk source, they are added by 
app_voicemail and db.c respectively.  This is perhaps why they are not 
included (I didn't write the first version of pyst, but that is why they 
are not in astxx::manager).  I am not completely opposed to having those 
commands included in the command set, although with pyst 0.3 it will be 
simple for users of the library to include custom actions (including 
your previous event handling action).

-- 
Matthew Nicholson
Digium