Hello, thanks for response. I certainly forgot to thank you all for great work. Right now I'm also running Freevo under win and seems quite OK.
About that database thing. My thoughts were more in direction of formal separation of datafetching from GUI displaying (this is obviously needed strategy for GUIs, cause they cannot wait for data to be fetched). I'm coming from small country and I have to fetch data on my own. For instance if I take the hypothetical weather plugin: it would be nice to display from some sort of standard format file (or database - whatever is more convenient) and data fetcher fills this file. In this way if I want to roll in my own data, I still get displaying OK. Maybe this could be useful also to other users. Regards, Robert. ----- Original Message ----- From: "Aubin Paul" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 25, 2003 2:32 PM Subject: Re: [Freevo-devel] Socket timeouts > On Sat, Oct 25, 2003 at 01:22:37PM +0200, Robert Rozman wrote: > > It would be certainly easier to connect them to database rather than to > > Freevo. At some point doing Freevo in backend/frontend would be necessary > > cause tommorow users will have more and more TVs, video outputs and PCs. So > > taking this step earlier could be advantage in future... > > Hypothetically, it could be possible to move the data into a database > and have the record server query that instead of the cached file, but > frankly, it wouldn't give a huge speed increase, and wouldn't make the > functionality much different. > > > Aubin > ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
