[mythtv-users] schedulesdirect: "proxy" fix as alternative to new MythTV build?

[Peter Watkins]

Apologies if this has been mentioned already; I haven't followed all
the SD/TMS/DD threads lately.

Looking at http://svn.mythtv.org/trac/attachment/ticket/3842/3842-head-v1.patch
I wonder about a fix external to MythTV. What about this approach for 
allowing "old" MythTV apps to use ScheduleDirect?

1) configure system where mythbackend runs to associate 
   hostname labs.zap2it.com with a local IP address
2) have a small app that listens for HTTP on the fake labs.zap2it.com
   IP address (would mean no httpd listening to 0.0.0.0 unless using
   something like a name-based virtual host / reverse proxy setup[0])
3) this small app requires HTTP Basic auth (as DD/Zap2it has) and
   uses that to authenticate to webservices.schedulesdirect.tmsdatadirect.com
4) this small app returns the data from the new SD web service to the caller

An old mythfilldatabase app would think it was connecting to the old DD
service, but this small app would actually hand the requests off to SD.

Such a "proxied web service" approach should allow even folks running fairly
old versions of MythTV to make minimal changes (i.e. no changes to their
actual MythTV/mythfilldatabase setups), although they would need to sign up
for SD and set up their lineups at SD, of course.

Thoughts?

-Peter

[0] and that's assuming that mythfilldatabase sends Host headers