Open GoogleCodeExporter opened 9 years ago
Addendum: this is about the Dutch ISP Xs4all.
Original comment by fe...@vangeuns.nl
on 10 Jun 2013 at 8:12
they've made a plugin for
plex,https://forums.plex.tv/index.php/topic/66954-channel-xs4all-webtv/ so
maybe someone who understands this sort of stuff can make it for xbmc
Original comment by ronvande...@gmail.com
on 8 Jan 2014 at 1:52
Perhaps somebody can make a Fiddler (http://fiddler2.com/) trace for this Plex
Add-on?
Original comment by basrie...@gmail.com
on 14 Jan 2014 at 10:28
No trace necessary, I've documented the public API (at least, most of it)
months ago. XS4All designed this for the exact use I'm suggesting.
https://github.com/Xs4allWebTV/Documentation/wiki
Original comment by fe...@vangeuns.nl
on 14 Jan 2014 at 11:09
Kewl, let me check this out and see what I can do. Thanks for the tip!
Original comment by basrie...@gmail.com
on 14 Jan 2014 at 11:12
BTW: I've made a basic XBMC plugin months ago, but I've ceased development
because the streams are not playable with XBMC's native player. Reason for this
is the lack of openssl support in XBMC's ffmpeg binary. I don't know what its
status is at this moment, but back then it was a real downer.
http://forum.xbmc.org/showthread.php?tid=166897
Original comment by fe...@vangeuns.nl
on 14 Jan 2014 at 11:18
even though I can read the api description it would be nice if I had a Fiddler
trace so I can use it to test it with on my non xs4all connection.
Original comment by basrie...@gmail.com
on 15 Jan 2014 at 8:14
Bitbucket Migration Message:
The XOT Google Code issue tracker is being migrated to Bitbucket. Please DO NOT
update these issues in Google Code, but rather at their new location. During
the migration the Bitbucket issue tracker will be unavailable.
More information on the migration can be found here:
http://www.rieter.net/content/2014/02/26/bitbucket-here-we-come/
The new issue tracker is located at:
https://bitbucket.org/basrieter/xbmc-online-tv/issues?status=new&status=open
Original comment by basrie...@gmail.com
on 28 Feb 2014 at 9:35
Original issue reported on code.google.com by
fe...@vangeuns.nl
on 10 Jun 2013 at 8:11