Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 161634" data-attributes="member: 21313">Thanks for the enthousiasm, you're the only one so far <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Since MediaPortal switched to client/server almost a year ago I think it could benefit from a more service-oriented approach, keep the clients really separate from the server.&nbsp; So that's why I'm proposing this route for the scheduling sub-system, it's a very good candidate to be split off.Especially now that we have Windows Communication Foundation in .NET 3.0, which makes it both easy and fast to set things up as services.&nbsp; Performance will not suffer significantly, but reliability and maintainability could be so much better.Damn, this almost sounds like an ad <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp; Apply ComSkip blocker...</blockquote>

[QUOTE="dvdfreak, post: 161634, member: 21313"] Thanks for the enthousiasm, you're the only one so far :) Since MediaPortal switched to client/server almost a year ago I think it could benefit from a more service-oriented approach, keep the clients really separate from the server. So that's why I'm proposing this route for the scheduling sub-system, it's a very good candidate to be split off. Especially now that we have Windows Communication Foundation in .NET 3.0, which makes it both easy [u]and[/u] fast to set things up as services. Performance will not suffer significantly, but reliability and maintainability could be so much better. Damn, this almost sounds like an ad ;) Apply ComSkip blocker... [/QUOTE]

Verification