Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 159920" data-attributes="member: 52082">I agree, SQL Server Express is freely redistributable and embeddable, making it a good solution as well. The only problem I see with that though is that redistribution is only allowed on Windows platforms. Not a huge deal, but a future port to Linux or Mac OS X is a possibility via Mono. If SQL Server was used for the DB backend of the TVServer, any future ports would be much more difficult.As far as MySQL goes, the full version could be redistributed with MediaPortal, but the embeddable version I believe is not free to redistribute. They charge for that.That is assuming that every single client on the network is connected directly to the database. A better design I think would be to have the TVServer act as a proxy for all clients. This would prevent database corruption and some client side errors from old clients trying to access new databases. You're right though, with the current design, that would be a major problem in switching to SQLite.That's good to know. ^^ It means other people are thinking along the same lines as I am.Just to be clear I am not trying to push SQLite down peoples throats, my real point is the user experience needs to be improved when it comes to installation of the TVServer. If that has already been identified and there are plans to address this, then my point is moot.</blockquote>

[QUOTE="fforde, post: 159920, member: 52082"] I agree, SQL Server Express is freely redistributable and embeddable, making it a good solution as well. The only problem I see with that though is that redistribution is only allowed on Windows platforms. Not a huge deal, but a future port to Linux or Mac OS X is a possibility via Mono. If SQL Server was used for the DB backend of the TVServer, any future ports would be much more difficult. As far as MySQL goes, the full version could be redistributed with MediaPortal, but the embeddable version I believe is not free to redistribute. They charge for that. That is assuming that every single client on the network is connected directly to the database. A better design I think would be to have the TVServer act as a proxy for all clients. This would prevent database corruption and some client side errors from old clients trying to access new databases. You're right though, with the current design, that would be a major problem in switching to SQLite. That's good to know. ^^ It means other people are thinking along the same lines as I am. Just to be clear I am not trying to push SQLite down peoples throats, my real point is the user experience needs to be improved when it comes to installation of the TVServer. If that has already been identified and there are plans to address this, then my point is moot. [/QUOTE]

Verification