Axel Pospischil wrote: >> You can download recordings from the backend using an URL like >> http://host:6544/Myth/GetRecording?ChanId=12345&StartTime=2008-07-15T00:00:00. >> > This would be a good solution. However the best it would be for the frontend > using the _ftp_ transfer protocol, because this really is the fastest way to > get big files over the network without causing additionally traffic/loss/... > . But you have to deal with what we have ;) > When downloading from mythbackend, I get 11.7MByte/s over fast ethernet. That should be good enough :) Besides, FTP is a horrible protocol.
> Just a few comments because I see you are going deeper into the problem: > There are two possible scenarios: > 1. Download to mytharchive frontend -> Process** locally > Yup, that's what happens. Mytharchive can already download files automatically if it determines that they are on a remote file system, so your other concern has already been addressed by the MythArchive developers. > > So laga I wish you good inspirations getting this (1.) to work ;) ... > Someday ;) > > Oh, it's working. ;) I just need to polish it a bit. Do you want to test the patch? Thanks for your input! -- mytharchive fails with python error https://bugs.launchpad.net/bugs/118700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
