Changes between Version 8 and Version 9 of FutureDevelopment


Ignore:
Timestamp:
03/30/06 10:42:51 (20 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FutureDevelopment

    v8 v9  
    66
    77 * A more standard communication protocol between the frontend/backend/etc.  Currently uses a custom protocol, and it would be nice to replace with something that's more of a standard.  '''Note:''' this really needs to be fairly efficient, since this is a common task.  Parsing XML queries/responses several hundred times a second really isn't a good thing to be spending CPU time on.  dbus a possibility?
    8  * uPNP support, both server and client.  Interoperability with CE devices, as a lot of them are starting to use uPNP for remote video playback. (David Blain)
     8 * uPNP (Universal Plug 'n' Play) support, both server and client.  Interoperability with CE devices, as a lot of them are starting to use uPNP for remote video playback. (David Blain)
    99 * Multicast streaming of video/live tv.
    1010 * Finish up Thor's work on mfd (Myth Frontend Daemon).  This would handle video streaming between machines, audio playing (music everywhere, not just in mythmusic), media importing (cd ripping), burning, etc.  The frontend process becomes more of just the UI.
    1111 * zeroconf/rendevous/bonjour/avahi/whatevertheycallitnow support for the frontend/backend.  Less setup work.  mfd already uses this.  Move the backend into a mfd process?  Could make the scheduler (ie., the master backend) be auto-promoted from existing backends on the network.
    12  * Live-tv rework - #340.
     12 * Live-tv rework - #340. http://www.zeroconf.org/ZeroconfAndUPnP.html
    1313 * UI rewrite - #12.  This actually encompasses more than the UI itself - one of the intents is to sanitize a lot of the code that's grown over the years, contributed by different people.  It's not terribly cohesive as it is.  Big task, I intend to write a larger doc once I have time for this.
    1414 * Abstract the SQL database somehow?  People doing embedded platforms want this, but it gets tricky due to access permissions/etc.  Might be better to make the frontend ask the backend for stuff, but it seems rather unwieldy to potentially bounce a query through the backend to the sql server, especially since that might be on a completely separate machine.