dbrobins Wrote:Ideally database-related structures should be hidden behind a wall, and on the "XBMC side" are existing XBMC structures (movies, artists, etc.), which it can lookup and store using an API that is not database, or even terribly database design specific. There need be no lock in to EAV/CR or not, for example; the database interfaces could be implemented that way, or not.
Indeed the data need not be store in a database at all. It could be served up by XML, UPnP or whatever.
My intent is to introduce a intermediary layer before the presentation that allows the fusing of multiple backend sources - local or remote.