Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: How to kill an svdrp connection from vdr ?



On 27/10/2004, at 2:49 AM, Klaus Schmidinger wrote:

Lauri Tischler wrote:
Nicolas Huillard wrote:

(I think a real client-server VDR would be a Good Idea - multiple
clients, multiple servers - separating boths commands, OSD, timers,
ouput device, etc. Multi-client SVDRP would be the first step)
Ummmm... Before jumping into rocketscience applications,
basic DVB operations should be implemented, mainly,
- multiple audioselections with preferred audio
- subtitles, ttxt and dvb
- anything else found in ETSI EN 300468
This is exactly why I never publish a TODO list for VDR.
Endless discussions about what is more important...

I understand this but people enjoy public discussions about what would be NICE to have. It helps when people nitpick your ideas so that you can refine them even if they won't be implemented by you in the short-term. However, I can also see that things can get a bit personal and none of us want to piss you off either :)

Now for my little question. With regards to the rocket-science. Do you intend to wait till the core parts (as you see them) of VDR are completed before making it more modular and built of multiple, replacable, extendable client/server components (if that's the best way to do it) ?

Just wanted to know your ultimate opinion (at the moment). Also if you intend to wait till the core functionality is done before doing anything like this do you not consider a loosely coupled collection of modules easier to develop, maintain and allow people to contribute to? Please remember I'm not criticizing, just genuinely curious about how you as the developer see these things.

Regards,
Michal Dobrzynski





Home | Main Index | Thread Index