utgg wrote: 
> Possibly, but the limelight URL redirects with '302 Moved Temporarily'
> code (so the redirection shouldn't be remembered if the HTTP
> implementation is behaving properly), and therefore requires two
> dependent HTTP fetches for each chunk or playlist fetch.
> 
> This looks to be just a different way of dynamic server load sharing,
> now I look at it:
> 
> On akamai the IP address for the static
> 'http://as-hls-uk-live.edgesuite.net' hostname changes frequently in the
> DNS lookup (requiring short TTL on the DNS response).
> 
> On limelight the IP address for the static
> 'as-hls-uk-live.bbcfmt.vo.llnwd.net' hostname seems to remain constant
> (and therefore cacheable), but the redirects to a continually changing
> hostname/IP address (presumably also with constant cacheable IP
> address).
> 
> If DNS lookups are a problem, I guess the limelight solution is
> preferable.
> 
> However, given the new information that the Apple iTunes implementation
> uses persistent connections, it is probably fine to stick with the same
> IP address on akamia (or redirected url on limelight) for quite a few
> successive chunk fetches to avoid the frequent full DNS lookups or
> redirections.I'm confused, mainly by everything you just said, but also as to 
> why
they have two different delivery methods.
Is one aimed at desktop and the other at mobile?

Another thought (as suggested a few weeks back by bpa) would be to make
the CDN selectable from the options gui and build the url in the
plugin.
Along with maybe uk/non-uk, high/low/med quality etc.

That way if anyone does hit a problem they could switch?



LMS Version: 7.9
TranquilPC T2-WHS-A3 - WHS 2011
2x Touch, 3x SB3
------------------------------------------------------------------------
bonze's Profile: http://forums.slimdevices.com/member.php?userid=6150
View this thread: http://forums.slimdevices.com/showthread.php?t=53229

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to