Rob Shortt wrote: > Dirk Meyer wrote: >> Rob Shortt wrote: >>>Modified: trunk/core/src/ipc/epg.py >> >> I'm not sure ipc/epg.py is the correct filename. I guess I need to >> write some more docs about how I think the structure should be. Maybe >> epg.py in core/src is the way to go, but I'm not sure yet. I will take >> a look at the code after the CeBIT (and we can replace epg with epg2 >> by that time, too) > > I have the same thoughts as you here, since core.ipc is really for mbus > and there's even some mbus code in ipc/__init__.py. I wasn't going to > bug you about it until after CeBIT :P.
Bug me now :) To the ipc code in Freevo. I want to put everything I need for communication between freevo processes in core/ipc. Since both webserver and freevo need to communicate with tvserver, it is in that dir. For epg the question is: is it a process in this way? Kaa vfs and thumb2 both start processes but they are internal stuff the user does not need to know, it feels like a normal function call. That's with this is not in freevo ipc. > I have some local tvserver changes too, and should have it all working > with epg2 really soon. I've simplified somethings and it looks like it > will work out well but I need to finish some changes and do some > testing. I guess I will have some time this weekend to take a look at it. BTW, feel free to merge your stuff into the main tree now, the CeBIT stuff is up and running and won't be updated anymore. > By the time you're done with CeBIT and have time to relax everything > should be in working order and we can do the switch. Time to relax? What does that mean? ;) Dischi -- UNIX _is_ user friendly - it's just selective about who its friends are!
pgpdNjQXbfNPb.pgp
Description: PGP signature
