Imho the only good solution is to have a single listener on a single port (http and/or https), and everything else is serviced by that listener. And this listener should have an API so you can plug in external services on URL's. And possible a default service so that URL's that don't have a service map can be routed to that default (which could then be OWIF for example).
Doesn't sound like the worst idea yet.
But I would go one (or multiple) steps further:
IMHO the whole E2 GUI should be rewritten (It's a pile of junk anyways), preferably using standards like HTML5, Ajax, ...
The WebInterface then wouldn't be something external anymore, but just the remote presentation of that GUI.
There would be three layers:
1. The one that does all the interaction with hardware (tuners) and stream servers and so on ...
2. The layer which prepares the content for presentation (Basically a web server with interfaces to layer 1)
3. The client layer, which is nothing else but a web browser optimized for TV output and control via a regular RC
Basically, layer 3 could then even be run on any (other) machine that is powerful enough to run a web browser and show video content on the screen.
Ok, ok, I'll open a different box of cigarettes, the last one must have been bad ...
Edited by SpaceRat, 15 May 2014 - 22:07.