Reply to thread

Message

<blockquote data-quote="smande00" data-source="post: 44566" data-attributes="member: 19339">Hello, I installed MediaPortal earlier this week and have so far been quite impressed (I actually found the project via the Xbox Media Center project which I believe Frodo founded as well).&nbsp; In any case, I've implemented a, for lack of a better term, client/server architecture of sorts by adding a new appsettings variable that holds a path to the database. I've then setup a shared folder on my server to hold a single repository for the database files.The idea was to enable multiple MediaPortal machines to access and update a single database rather than synchronizing several machines whenever media was added to my library. Looks like it works well enough so far (for reading anyways, I haven't tried writing to the db yet). I've got a couple quick questions: 1) Is anyone working on something similar?2) Right now I'm using the app.config file to store the database&nbsp; path, is there a more appropriate place?3) Does this warrant submitting a patch when I've completed it?4) Is it appropriate to distribute dlls &amp; instructions to anyone wishing to try it out on their system (don't want to step on any toes).5) Are you still reading this list?By the way fantastic job maintaining the project in CVS. I fully expected to spend a day figuring out why it wasn't building. I LOVE it when things *just work*.Keep up the good work!</blockquote>

[QUOTE="smande00, post: 44566, member: 19339"] Hello, I installed MediaPortal earlier this week and have so far been quite impressed (I actually found the project via the Xbox Media Center project which I believe Frodo founded as well). In any case, I've implemented a, for lack of a better term, client/server architecture of sorts by adding a new appsettings variable that holds a path to the database. I've then setup a shared folder on my server to hold a single repository for the database files. The idea was to enable multiple MediaPortal machines to access and update a single database rather than synchronizing several machines whenever media was added to my library. Looks like it works well enough so far (for reading anyways, I haven't tried writing to the db yet). I've got a couple quick questions: 1) Is anyone working on something similar? 2) Right now I'm using the app.config file to store the database path, is there a more appropriate place? 3) Does this warrant submitting a patch when I've completed it? 4) Is it appropriate to distribute dlls & instructions to anyone wishing to try it out on their system (don't want to step on any toes). 5) Are you still reading this list? By the way fantastic job maintaining the project in CVS. I fully expected to spend a day figuring out why it wasn't building. I LOVE it when things *just work*. Keep up the good work! [/QUOTE]

Verification