Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 364307" data-attributes="member: 21313">I'd just like to add that the whole idea of &quot;integration&quot; seems to be looked at differently by different people.&nbsp; I'm not unbiased of course, but I think the architecture of For The Record has proven itself over the last year or so.&nbsp; We often get positive feedback about the stability of the system.I see no reason to mess with that: the core of For The Record is just fine as it is (which doesn't mean it won't keep improving over time, of course it will).So, simply releasing the sources and try to make a melting pot with the current source code of TV server would make a rather ugly mess (just my honest opinion).&nbsp; I sort of keep repeating myself, but the best road to closer integration would be to fine-tune the recorder/tuner interface from the core services into the recording system.&nbsp; This is perfectly in line with the service oriented architecture in which I continue to firmly believe, and which as I just mentioned has proven to be very effective and solid.Additionaly, improving the GUI plugin would also be the way to go.&nbsp; Here For The Record actually follows the same path as the original TVPlugin: provide a user interface onto your core server (be it local or remote on your LAN).&nbsp; The main difference, once more, being that For The Record uses the SOA architecture here, so the client is much more cleanly separated from the server than the original TVPlugin.It's unclear to me what Team MediaPortal thinks about this potential road (to success? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).</blockquote>

[QUOTE="dvdfreak, post: 364307, member: 21313"] I'd just like to add that the whole idea of "integration" seems to be looked at differently by different people. I'm not unbiased of course, but I think the architecture of [b]For The Record[/b] has proven itself over the last year or so. We often get positive feedback about the stability of the system. I see no reason to mess with that: the core of [b]For The Record[/b] is just fine as it is (which doesn't mean it won't keep improving over time, of course it will). So, simply releasing the sources and try to make a melting pot with the current source code of TV server would make a rather ugly mess (just my honest opinion). I sort of keep repeating myself, but the best road to closer integration would be to fine-tune the recorder/tuner interface from the core services into the recording system. This is perfectly in line with the service oriented architecture in which I continue to firmly believe, and which as I just mentioned has proven to be very effective and solid. Additionaly, improving the GUI plugin would also be the way to go. Here [b]For The Record[/b] actually follows the same path as the original TVPlugin: provide a user interface onto your core server (be it local or remote on your LAN). The main difference, once more, being that [b]For The Record[/b] uses the SOA architecture here, so the client is much more cleanly separated from the server than the original TVPlugin. It's unclear to me what Team MediaPortal thinks about this potential road (to success? :)). [/QUOTE]

Verification