Re: [GNUe] SIP Witch/GNUE TMS

[David Sugar]

It probably does make more sense to push it directly from the client,
especially since I also wanted to have a simple "export" that saves an
xml config on the filesystem as well as the option to push it to the
switch directly.  The pushing part can either be done in python, or
perhaps simply driving wget...

The application overall so far is rather small and simple, though I may
later add things like help desk type functionality, publishing of phone
directories, etc.

gnue-forms made great sense as a starting point as it is largely a
crud-type application, with rather simple tables for servers, users,
profiles, groups, gateways, etc.  The ideal format, though, I think
would be a mixed grid/record form layout view.

Reinhard Mueller wrote:
> Hi, David!
> 
> Nice to hear that you're using gnue-forms for this!
> 
> Am Samstag, den 28.06.2008, 23:23 -0400 schrieb David Sugar:
>> I have a question, however.  One of the things we have to do is
>> generate a sipwitch XML config file out of the database, and then push
>> it out over http post to each call node.  Is this the kind of task
>> that one might be able to make use of appserver for?
> 
> Actually I wouldn't use appserver for that, but I'd rather write some
> Python code that does that and bind it to a button in the form. AFAIU,
> the application would be comparably simple (maybe something that you'd
> run against an SQLite database) and running an appserver for this might
> be overkill.
> 
> If the whole TMS gets complex enough to justify the use for appserver,
> you would certainly also put the pushing of the XML into the appserver
> layer, of course.
> 
> So I guess the answer depends on the overall size of the TSM
> application.
> 
> Thanks,
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Gnue mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnue

dyfet.vcf
Description: Vcard