mailrus alodiah walcott

[Jacinto Dieujuste]

Usually power off puck or come out of netflix load another app then back to netflix would normally resolve it. However today none of this works it sticks at 20% on every attempt to view. Have had to resort to using the native TV app this works fine. How is something this flawed not picked up in testing?

I think the cause of such issues is all down to how Sky/Comcast's streaming platform works. All the apps on Glass & Stream are hosted on a server, not on the device itself. This is the root cause of the general sluggishness of the interface and the reason apps can take up to 30 seconds to buffer up to even just HD quality.

The servers are clearly under an ever increasing load as more and more people sign up to the service so there's an awful lot of data being sent up and down to those servers from many, many connections. There's clearly a lack of cache space in the pucks as they simply don't cope well under any sort of pressure. Fast forwarding and rewinding for example, is such a slow & glitchy affair (even on a basic HD stream) that it's already showing how much it struggles.

With Netflix, they use higher bit-rates, Dolby Vision, HDR10, Atmos etc and therefore have to send a larger data stream back to the puck from the server. Also, with the actual app hosted on the server, that server has to communicate first with Netflix's servers in order to receive the stream of the programme you, the customer, has selected. This stream then has to be sent down to the puck. This all means the server is under a lot of pressure, particularly when there are potentially thousands of people trying to access Netflix from a puck or Glass TV at the same time.

The only real solution I've found is to just not use the puck for third party apps. I use the native TV apps or my Apple TV 4K box and have no issues whatsoever. Netflix has no buffering whatsoever and HD streams from the likes of the Channel 4 app play instantly in full quality.

Stream is absolutely fine for live TV, I've never had an issue with that (though it does take a few seconds for even those HD streams to reach full quality on a wired 500Mbmps ethernet connection) so that's what we use it for. Turn it on, select something to watch live and leave it - that works perfectly well. It's everything else that's problematic.

@DJBSuffolk and others. This problem has been going on for some time and Sky & Netflix were working on a solution. Until a solution is found there are a couple of ways that will generally clear the problem;

Started to have this issue recently. Reload Netflix didn't work. What did however was quickly starting up a number of the other apps and then going back to Netflix after opening about 2 or 3, just to get it to sort of flush the underlying Netflix process from memory.

If the Netflix screen starts from scratch again with the noise and the live previews on the Home Screen then the app has been successfully restarted.

This is still ongoing. I have it with Netflix and Amazon video. I am considering buying a smart tv (I didn't think i needed to with sky stream!) so I can watch other programmes. SKY- is there an update on this issue??

I've just gone to Sky stream and having the same 20% issues. Couldn't watch anything. Also having problems with BBC iPlayer just blank screen or whirling circle. I much preferred recordings than stream but will contact sky as I've literally just joined them.

Netflix is testing a redesigned version of its TV app, reports The Verge, marking the first major overhaul to the app in the last decade. The new design is a notable departure from the current look, but it is more modern and puts more information about content front and center.

Customers were reportedly performing "eye gymnastics" looking around to different parts of the home screen in an attempt to find a show or movie to watch, so Netflix wanted to simplify the navigation experience. "We really wanted members to have an easier time figuring out if a title is right for them," Netflix senior director of product Pat Flemming told The Verge.

The static tiles for TV shows and movies are being replaced with tiles that extend when the remote lands on them, making information like the trailer and description more centralized. Right now, when scrolling through content, show or movie information is displayed at the top of the screen. With the updated interface, that information is shown in the middle of the display, and tiles for other shows are pushed to the side.

Netflix plans to replace the left side navigation menu with a top bar menu that features search, home, shows, movies, and My Netflix, with the menu accessible by pressing the back button on the remote. The current Categories and New and Popular tabs will be removed, but New and Popular will be replaced with the My Netflix recommendations, and Categories will be available from the search tab.

MacRumors attracts a broad audience of both consumers and professionals interested in the latest technologies and products. We also boast an active community focused on purchasing decisions and technical aspects of the iPhone, iPad, Mac, and other Apple platforms.

Feign is a declarative web service client. It makes writing web service clients easier. To use Feign create an interface and annotate it. It has pluggable annotation support including Feign annotations and JAX-RS annotations. Feign also supports pluggable encoders and decoders. Spring Cloud adds support for Spring MVC annotations and for using the same HttpMessageConverters used by default in Spring Web. Spring Cloud integrates Ribbon and Eureka to provide a load balanced http client when using Feign.

To include Feign in your project use the starter with group org.springframework.cloudand artifact id spring-cloud-starter-openfeign. See the Spring Cloud Project pagefor details on setting up your build system with the current Spring Cloud Release Train.

In the @FeignClient annotation the String value ("stores" above) isan arbitrary client name, which is used to create a Ribbon loadbalancer (see below for details of Ribbonsupport). You can also specify a URL using the url attribute(absolute value or just a hostname). The name of the bean in theapplication context is the fully qualified name of the interface.To specify your own alias value you can use the qualifier valueof the @FeignClient annotation.

FooConfiguration does not need to be annotated with @Configuration. However, if it is, then take care to exclude it from any @ComponentScan that would otherwise include this configuration as it will become the default source for feign.Decoder, feign.Encoder, feign.Contract, etc., when specified. This can be avoided by putting it in a separate, non-overlapping package from any @ComponentScan or @SpringBootApplication, or it can be explicitly excluded in @ComponentScan.

The OkHttpClient and ApacheHttpClient feign clients can be used by setting feign.okhttp.enabled or feign.httpclient.enabled to true, respectively, and having them on the classpath.You can customize the HTTP client used by providing a bean of either ClosableHttpClient when using Apache or OkHttpClient whe using OK HTTP.

Default configurations can be specified in the @EnableFeignClients attribute defaultConfiguration in a similar manner as described above. The difference is that this configuration will apply to all feign clients.

If we create both @Configuration bean and configuration properties, configuration properties will win.It will override @Configuration values. But if you want to change the priority to @Configuration,you can change feign.client.default-to-properties to false.

In some cases it might be necessary to customize your Feign Clients in a way that is notpossible using the methods above. In this case you can create Clients using theFeign Builder API. Below is an examplewhich creates two Feign Clients with the same interface but configures each one witha separate request interceptor.

The Feign Contract object defines what annotations and values are valid on interfaces. Theautowired Contract bean provides supports for SpringMVC annotations, instead ofthe default Feign native annotations.

If Hystrix is on the classpath and feign.hystrix.enabled=true, Feign will wrap all methods with a circuit breaker. Returning a com.netflix.hystrix.HystrixCommand is also available. This lets you use reactive patterns (with a call to .toObservable() or .observe() or asynchronous use (with a call to .queue()).

Prior to the Spring Cloud Dalston release, if Hystrix was on the classpath Feign would have wrappedall methods in a circuit breaker by default. This default behavior was changed in Spring Cloud Dalston infavor for an opt-in approach.

Hystrix supports the notion of a fallback: a default code path that is executed when they circuit is open or there is an error. To enable fallbacks for a given @FeignClient set the fallback attribute to the class name that implements the fallback. You also need to declare your implementation as a Spring bean.

There is a limitation with the implementation of fallbacks in Feign and how Hystrix fallbacks work. Fallbacks are currently not supported for methods that return com.netflix.hystrix.HystrixCommand and rx.Observable.

A logger is created for each Feign client created. By default the name of the logger is the full class name of the interface used to create the Feign client. Feign logging only responds to the DEBUG level.

As of today, subscribers watching Netflix titles on their mobile devices can get a video preview before they commit. Previews have long been available on Netflix's TV and desktop interfaces, and now they're coming to mobile devices as well. Apple iOS users can watch previews starting today, while Android viewers will get them "soon."

Mobile users will be able to view previews in a vertical interface, so they won't need to leave the user interface or turn their screens. Subscribers can tap to add a video to their saved list, or swipe or tap on the screen to call up a different preview.

90f70e40cf