home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Use WebService between Server and Client
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chrispi" data-source="post: 125419" data-attributes="member: 20307"><p>Hello guys,</p><p></p><p>Let me clarify some points:</p><p></p><p>1) VS 2005 uses his own web server to debug web applications or a web service. This has nothing to do with hosting a web service inside a EXE. The XP-Version (Home, Profesional) is not an issue here because you can host a web service even on XP home without having any kind of Web Server installed.</p><p></p><p>2) Media Portal does not need to be ported to the .NET Framework 3.0 because the new Framework is based on the CLR 2.0. The .NET Framwork 3.0 is the .NET Framework 2.0 plus WCF and some other "Libraries". So It's not really a new version and Media Portal will run fine on V3.0 without any changes or recompilation.</p><p></p><p>3) With WCF you can switch with a config parameter between Web Services for compatibility or Binary Format (comparable with remoting) for best speed. Code changes are not requred so the user can decide what to use. Using WCF you get the best of both worlds.</p><p></p><p>Microsoft does strongly recommand not to use remoting anymore because it is outdated. This statement is more than 1 year old. My concern is, that remoting will be removed from future versions of the .NET Framework.</p><p></p><p>Also the advantages of the binary format compared to Web Services are not so big so WCF with SOAP protocol (= Web Service) would be the best solution for the TV Engine V0.3.</p><p></p><p>Regards,</p><p>Christoph</p></blockquote><p></p>
[QUOTE="chrispi, post: 125419, member: 20307"] Hello guys, Let me clarify some points: 1) VS 2005 uses his own web server to debug web applications or a web service. This has nothing to do with hosting a web service inside a EXE. The XP-Version (Home, Profesional) is not an issue here because you can host a web service even on XP home without having any kind of Web Server installed. 2) Media Portal does not need to be ported to the .NET Framework 3.0 because the new Framework is based on the CLR 2.0. The .NET Framwork 3.0 is the .NET Framework 2.0 plus WCF and some other "Libraries". So It's not really a new version and Media Portal will run fine on V3.0 without any changes or recompilation. 3) With WCF you can switch with a config parameter between Web Services for compatibility or Binary Format (comparable with remoting) for best speed. Code changes are not requred so the user can decide what to use. Using WCF you get the best of both worlds. Microsoft does strongly recommand not to use remoting anymore because it is outdated. This statement is more than 1 year old. My concern is, that remoting will be removed from future versions of the .NET Framework. Also the advantages of the binary format compared to Web Services are not so big so WCF with SOAP protocol (= Web Service) would be the best solution for the TV Engine V0.3. Regards, Christoph [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Use WebService between Server and Client
Contact us
RSS
Top
Bottom