> Hi all,
>
> I'm doing quite a lot of changes to local_config variables, at the
> moment. The webconfig tools has revealed that we have rather
> inconsistent names for the certain items. So I would like to fix these,
> if you know of any inconsistencies please let me know.

Good idea, all the better for people coming to freevo for the first time.

>
> I would like to do release 1.7.4 on 15 Nov 2007 and so I would like to
> finish off the variable renaming before Sunday and then make a rel-1-7
> branch. After this the translators can get to work :)

Better get some of those patches I've been working on into sourceforge :-)

> The rel-1 branch will then be updated with the kaa.notifier code and I
> would like to release this as 1.8.0 in the middle of December.
> Also for 1.8.0 I would also like to remove Twisted from the
> recordserver, which I'm working on at the moment, and update the
> webserver to allow Twisted-2.5 to work. If anyone want to fix the
> webserver then please do.
>

One of the things I've being playing with specifically to replace Twisted
in the recordserver is Pyro. I had the problem that the xmlrpc interface
is way too slow for me (recordserver is a PIII 500 and the time to bring
up the TV program details/record screen was a couple of seconds). I've
been running Pyro for a while now and have found it very very fast in
comparison to xmlrpc. Also it is a lot simpler to implement, if you're
interested Duncan I'll send you my modified files (which contain the
xmlrpc and pyro code, both active for comparisons).

Cheers

Adam


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to