Re: [Freevo-devel] Re: kaa.epg sucks

2005-10-11 Thread Jason Tackaberry
On Tue, 2005-10-11 at 16:01 -0300, Rob Shortt wrote: > If would be good if you can add that kind of authentication. I don't > think encryption here is a big deal, we're talking LAN here. Ok, I will add it. > in a situation where I needed encryption I'd use ipsec which is easy to > set up. True

Re: [Freevo-devel] Re: kaa.epg sucks

2005-10-11 Thread Jason Tackaberry
On Tue, 2005-10-11 at 13:48 -0400, Jason Tackaberry wrote: > Probably not a bad idea to do prefetches like that. There's a pretty > high initial overhead, so it's better to get more rows than you need. > For example, querying for the next 2 hours of program data takes 0.1 > seconds and returns 200

Re: [Freevo-devel] Re: kaa.epg sucks

2005-10-11 Thread Rob Shortt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason Tackaberry wrote: > On Tue, 2005-10-11 at 17:09 +0200, Dirk Meyer wrote: > >>We should keep some things in mind. First, your IPC code is nice but >>not secure. Everyone can connect to the server and call python >>functions and such things. > >

Re: [Freevo-devel] Re: kaa.epg sucks

2005-10-11 Thread Jason Tackaberry
On Tue, 2005-10-11 at 17:09 +0200, Dirk Meyer wrote: > We should keep some things in mind. First, your IPC code is nice but > not secure. Everyone can connect to the server and call python > functions and such things. I can add authentication. But the data still wouldn't be encrypted, so in any c

[Freevo-devel] Re: kaa.epg sucks

2005-10-11 Thread Dirk Meyer
Hi, here some thoughts about kaa.epg Jason Tackaberry wrote: >> I wonder... if we used kaa.vfs in kaa.epg, would it be easier to wrap it >> up with ipc or mbus? I still have a strong feeling that the EPG should >> be client / server oriented. > > I agree fully that it should be client/server. A