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
Submit: code patches (MediaPortal/TV-Server/etc.)
DVB-IP scanning improvements
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="AlexPlas" data-source="post: 748467" data-attributes="member: 24336"><p>Hi georgius</p><p></p><p>I almost decided to remove network interface (NI) selection from my patch <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> Just few words in my defense.</p><p></p><p>I think NI selection is applicable to datagram based protocols (UDP, RTP) only. With stream based protocols like HTTP you establish connection and then you doesn't matter where is bound your local end of the socket, you will receive data anyway. In UDP and RTP your local end act as a kind of server and right binding is pretty important to receive data. </p><p></p><p>I think changing HTTP or any other new protocols (like KARTINA) undesirable, because it has complex structure and it's very hard to add something there and not break the URL. In contrast, UDP and RTP URLs have very simple format (unfortunately there is no standard), which can be easily parsed and recombined.</p><p></p><p>I have checked M3U files from the TuningParameters folder and there are few playlists where network interface addresses are already hardcoded in URLs. I think it is much worse than reasonable changing URLs during channels scanning. Users like just choose appropriate tuning parameters scan channels and watch it.</p></blockquote><p></p>
[QUOTE="AlexPlas, post: 748467, member: 24336"] Hi georgius I almost decided to remove network interface (NI) selection from my patch :) Just few words in my defense. I think NI selection is applicable to datagram based protocols (UDP, RTP) only. With stream based protocols like HTTP you establish connection and then you doesn't matter where is bound your local end of the socket, you will receive data anyway. In UDP and RTP your local end act as a kind of server and right binding is pretty important to receive data. I think changing HTTP or any other new protocols (like KARTINA) undesirable, because it has complex structure and it's very hard to add something there and not break the URL. In contrast, UDP and RTP URLs have very simple format (unfortunately there is no standard), which can be easily parsed and recombined. I have checked M3U files from the TuningParameters folder and there are few playlists where network interface addresses are already hardcoded in URLs. I think it is much worse than reasonable changing URLs during channels scanning. Users like just choose appropriate tuning parameters scan channels and watch it. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Submit: code patches (MediaPortal/TV-Server/etc.)
DVB-IP scanning improvements
Contact us
RSS
Top
Bottom