When handled properly threading is not a problem.An open-source, enhanced version of the SQLite database engine for Windows
Please reconsider looking at file-based DBMS alternatives. There are a number to choose from these days including SQLite, HSQLDB, Derby DB, VistaDB Express, etc.
I really want to ditch WMC and MediaPortal is the closest thing to it. One of the main things keeping me away at the moment is that it's still too bloated. I don't want to run a MS SQL / MySQL server just to watch TV. I was trying to get away from all this when I ditched MythTV. I don't particularly like the client/server TV architecture either, but that's a different story.
Having an embedded DB will help make the package as self-contained as possible. I personally think this is a must for the future of the project.
this is fine for single client, what about us who have multiple clients running off the TV server
wouldn't that be an issue
Agree! Me personally I would even appreciate moving the rest of the databases also from sqlite to mysql - since it's running anyway and much easier to tweak. I understand, that for a simple standalone tv-appl this seems oversized - but there are solutions like DVB-Viewer to cover this...Please reconsider looking at file-based DBMS alternatives. There are a number to choose from these days including SQLite, HSQLDB, Derby DB, VistaDB Express, etc.
I really want to ditch WMC and MediaPortal is the closest thing to it. One of the main things keeping me away at the moment is that it's still too bloated. I don't want to run a MS SQL / MySQL server just to watch TV. I was trying to get away from all this when I ditched MythTV. I don't particularly like the client/server TV architecture either, but that's a different story.
Having an embedded DB will help make the package as self-contained as possible. I personally think this is a must for the future of the project.
this is fine for single client, what about us who have multiple clients running off the TV server
wouldn't that be an issue