On Mar 19, 2012, at 14:01 01, James Harrison wrote: > If you're hosting this from a residential ISP then you should probably > consider if it's really suitable for remotely running Rivendell over, > particularly if you plan to move audio about. Even if you don't, > MySQL/Rivendell prefers low-latency conditions and reliable connectivity (no > to low packet loss etc).
Correct. In addition to the dynamic addressing issue already referenced, using 'best effort' public Internet connectivity between RD hosts will be likely to cause you problems due to dropped UDP packets. If provisioning a business-class network is not an option, then your best bet may be to employ a TCP-based tunnel between the two systems across the unreliable network. This will make overall latency somewhat worse, but will at least solve the dynamic addressing and dropped packet problems. Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | A room without books is like a body without a soul. | | -- Cicero | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
