Reply to thread

Message

<blockquote data-quote="georgius" data-source="post: 748090" data-attributes="member: 107951">Interesting idea, but I have some remarks. Routing network communication through specified network interface should be solved in general way. This problem should be solved not only for IP addresses in numeric format, but also for URLs (e.g. udp://myprovider<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" />ort, <a href="http://provider.com/channel" target="_blank">http://provider.com/channel</a>). I think that we should not encode network interface into URL directly (or at least not into URL written in playlist, this URL should be sent to filter in unchanged form). We also should not use network interface IP address, because whole URL sent to filter will be written to database. Network interface IP address for users with DHCP will change (in worst case can change also network mask).Because filter is written in C++ we cannot use managed classes to exchange parameters between TV-Server Configuration, TvServer and filter <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />So I think that we should use some kind of &quot;protocol&quot;. I suggest to encode needed parameters for filter to URL in next way: param1=value1|param2=value2|...|paramN=valueN (if in some value have to be written pipe character, it will be doubled, e.g. needed value 'abc|123' will be written as 'abc||123'). The name of parameters should be defined somewhere in TvService source code, for begining we need url and interface. So, url in playlist &quot;udp://@233.62.90.1:1234&quot; and interface with name &quot;Local Area Connection&quot; will be encoded into this url: url=udp://@233.62.90.1:1234|interface=Local Area Connection; without specified interface: url=udp://@233.62.90.1:1234.What do you think about this?</blockquote>

[QUOTE="georgius, post: 748090, member: 107951"] Interesting idea, but I have some remarks. Routing network communication through specified network interface should be solved in general way. This problem should be solved not only for IP addresses in numeric format, but also for URLs (e.g. udp://myprovider:port, [url]http://provider.com/channel[/url]). I think that we should not encode network interface into URL directly (or at least not into URL written in playlist, this URL should be sent to filter in unchanged form). We also should not use network interface IP address, because whole URL sent to filter will be written to database. Network interface IP address for users with DHCP will change (in worst case can change also network mask). Because filter is written in C++ we cannot use managed classes to exchange parameters between TV-Server Configuration, TvServer and filter :( So I think that we should use some kind of "protocol". I suggest to encode needed parameters for filter to URL in next way: param1=value1|param2=value2|...|paramN=valueN (if in some value have to be written pipe character, it will be doubled, e.g. needed value 'abc|123' will be written as 'abc||123'). The name of parameters should be defined somewhere in TvService source code, for begining we need url and interface. So, url in playlist "udp://@233.62.90.1:1234" and interface with name "Local Area Connection" will be encoded into this url: url=udp://@233.62.90.1:1234|interface=Local Area Connection; without specified interface: url=udp://@233.62.90.1:1234. What do you think about this? [/QUOTE]

Verification