 So I am working as the senior content editor for this show, and today I will talk about how to achieve a good post physical agency. So the main goal when I am working with an enterprise, the main goal is the best to achieve a good post physical agency. So today I was just talking to the rich people and I just saw this picture. So I didn't say that one is wrong here. So the GS that is getting downloaded faster, fast faster, which is compiled as an expert in the best user experience. But again, we are into that. But there are some other cities in the India where people are not able to upload high-end data. So the busy again, download times matter for the fluid network and the passing time that is the fluid devices. So in the last one important thing for this week is post printing and app. So we all are aware that by checking and by spreading the latest, we can achieve better side performance and better feedback. But it is also often with something like this. So let's say how do we do it all. Because there is combination like high-end device, high-end device, high-end device, high-end device, high-end device, high-end device, high-end device, high-end device. So this printing will be there for all of the activities. The first, the best, everything. So once there might be a case where the things like the chance to read by the people, even stream your response in chance. The same way you are sending your Jays code or status code in chance to read. So let's see how we are defending it. So Jays and Stream is really a continuous stream of meaningful, possible, and engineering is an object of this kind of a life. So what I mean by this is that let's say a piece of book might show up in case of any problem. There is a listing. And in that listing you get the thousand components in the right, thousand objects. So you stream those objects from right now. So what problem it solved? So already we have solved problems by expecting Jays and status code. Now this problem of large distance, so we solved it. So here you have a problem. So you might be having some API code which requires to be able to make an answer on the API code. Another thing is if the response can be solved by your server, it can be read. It can be slow and good. So for example, if you are searching your file, something in the grid side, and the SOM that is going to be delivered is of a great deal. And something goes wrong at the end. The resources and the time just for 70 years is missing. So I divide the things into more things. That is the limit. Some of it is pretty neat. No one really wants to solve the second case, right? Everyone wants to solve the first case. So sometimes there is a business constraint that you can't get in post-punition. In the case of all my show, you can't pay it. Because if you pay it in fact, the listing of others who want to go on second case is not a question. It doesn't really have to be a question. They will go out on their second case. So you really can't get it in such cases. Again, at the end of that, not in the case plan, longer it will take to solve it all. Longer it will take to solve it all. It wants to do the same objective. You are doing the same. So it is larger that it will take longer to solve it all. And it will read also. The illustration is taken again at the end of the screen. So if you are on second case, it is greater that it will take longer to solve it all. So this bar is bigger. And that will really handle your problem. So half it works. So basically the same way we found our case in cases 5, maybe we found your case in response. So this response should be chunked. Unlike case and case system thing, it will take upper case to create the user object. To create the user object. So the upper case is 64k. If there is a data demand that will be converted into the next step, then that is 30 years of this problem. Because still it is new to browser. So it has to calculate that for all problems. So this is like an example. So the first step is showing that the streaming how it will work. The second thing is how you write. You will aggregate it and you will understand that you will pass it. So that is the difference. When stream is played, you will see that when it is getting loaded, one by one. And if the bar within the store bar is included, that can be followed. That means it is greater stage 1. This is for downloading to mobile. It was trained last year. When aggregate is played, what it does? That waits for the last slide to come. That aggregates all the data and pass it in the user object. And then after it records the stream. So that was created using the graded data and the backcourt data. So that is how it influences. So first standard was quick. So maybe this scenario was taken to slow and it was going to be faster. So as soon as the data was slow, it was possible to render it. As soon as the data was backcourt and conservative, it rendered as it is. In case of accumulation, it waited for the last slide to come. Accumulated it, passed it and then it was rendered. So you could see the difference. It was very distracting in this way. And it appeared at one point in the slide for the first render and the last one. Let's explain it now. So the experience is not always the same. It has to be done in the collaboration of Saturday and Sunday. So the internet in small changes had to be back at its best. So let me discuss this one. This is Bahubali, 32 response. The movie was played and this was the rest of the story. So there was a quantity, 8% of the movie was made in Mumbai. You can see the raw response size was 8.99. Which is more than the entire bundle of, entire JS bundle of the movie. So that is really quite strange. So sometimes what happens when you design an interesting page? We are really not aware of what size of data we are getting and handling. So roughly you can see that it is kind of a long term deal. That means create tons of all of your questions. So the definition of take-to-take, definition of difference today, create many food and pass it a chance. So this is the list and each of set is many food and pass it a chance. So what I will do? I will iterate over the entire line and I will still write. By creating tons for each bundle. I don't know whether to put it in. So basically it is simple. Just iterate over your collection of data. Normally when you are dealing with this thing, it is a collection of same kind of data. It iterate over case, string it how it, store it from there. For example, it can store it in the most amount of it. Or it can store it back to it. Which is the key element. Now there is a schedule. The upper part of the anything until 64 days. So it has to be digitized. So the chunk which is beyond that size, size has to be digitized. Can it go to the next? So 10 days. This is the 10 days I have done. That 10 days. That 10 days. It will go to the next day. So this is just an example of that. First time it was 50 days. Another is showing days. So 10 days, 10 days. Something different than the 10 days one. Now there is a 20 days schedule. It is 10 days free. And each free is showing 6 shows in a day. So that will be 60 shows a day. So that can be a lot. So the jump is 67 days. So what it will do? That it will have to come in 62 days. So there will be 2 turns. That will be present one day. Second thing is streamed at 19.45. This is the next 10 days. Now now what we do? We just write response dot end of response dot relation to do. To provide response in time. But here it is not that. What can be done is, whatever the terms that we created, write it down that it gives you for the life. So what do we need? We need to get over all the terms. They are written for the wire. We just write it down. And then we send the other term over. Now, except if you do that L, that means nothing is possible. So in the last 10 days that number, what we will do? We just add, we will close the connection. So this is how it will be shown here. It is ready. Now again, So what are the changes that we are going to do? It should be able to introduce the address in this cycle, in the picture, in the picture, before and after. This is pretty straightforward. You test it. You have to recognize that if you have an availability code or if you have a lot of numbers, you will have to find the number. In response, you get clear. And readers are getting the point into the question. This is string. There is something read on it. So to read it further, readers have to trace it. And instead of that, this is pretty a thousand to read this way. You get the start. Then what you do is write a function that will keep reading the chunks until it comes and comes in the last one. So inside the function, what kind of function is it? Just read it. This is what reader is asking. And here, readers are reading with read chunks and when the chunk reading is finished, in response, you get to the question. The question is when and the color is done. Value is particularly unsanitary and it could be a right question. And this is done with thank you that reader's response has finished or not. So done. And we will report the value in the text. You can convert it to the question format and you will be in the pre-score type state to set in the state. So as soon as chunks starts coming, you are updating the state. You are pushing the value in the state. So that after you get done, let us go through it. The other is this is to talk this is to read the chunk and then there is the question. So there are a lot of challenges that we have to deal with. The first thing is take into account the online process. Basically, you have to process some part of the data of the system. So it has to be processed. In case of moving, for example, certain moving can be so things are fixed. So once the data is fixed, you can chunk it. So that is it. Your business might want to attend problems like UC problems, maybe it is higher so it will be better. Some other sources are written on it or something. So make sure you are not writing it. So probably you might have to make another error. So these are some challenges that can be overcome. There are some challenges that you can check out. So these are the earlier problems that I mentioned. You can do it by yourself. Any questions? Any other? My question is for you. So have you looked at the cases that came into India in the summer? Because it allows you to restrict your layoff in cases using CSP itself. So that is really good. Can we handle the government? So I see that as a way to do all the process. I mean, we are actors but it depends on what supports them. We can do this. Because we did not want to speak for every browser we had a customer base. We did not want to lose that. So in the word browser, I express the word in your sense that I want to see it. So is that for making sure that the chance is coming on us? So it is for to ensure that the service is going on the right way on the left side. And this is not a happy environment. So when it comes to so you are on the wrong side. You are ready to go on the wrong side. So it has to be okay. And that is the problem. So you have this problem. You can get whatever you must do according to the process. Before finding the chance you score them and then string them forward. Make sure before sending another chance you don't have it. This is for the best option. The thing is they don't have this problem and they will start. In that case you will see the task manager or activity manager Okay. So that is actually a very nice question. One monitor on your console always on. Let's hope you find it. Make sure that all of your entry component is handled correctly. If the company doesn't break your variables we have to keep everything segregated. That's the major thing when you are using it. Just like you have to normalize the component. It's very similar to react the candle that you have to make everything separate. If you put in everything the second time chance are you might over. And you will get my power value. So make sure you do that. You have to show that. Like you said like work chunky you have to show the server side as well as the client side. The chunky one to the client and then as well as the server side. So I have to mention that it is like you have to check the browser component everything. So suppose if your problem is not compatible. What's the problem because you have opted for each other component. How to make this to the server to create chance. So creating chance is the process which is done on the server. But the issue is that you can probably have a high order component that can handle condition of it. So that is there. If it is not available then you can use the my default language that you are using as the rest of the environment. Explosions for normal doctors help you. What are your questions? My question was what are the end-to-end. So you used the previews. What are the previews that are included by the end-to-end. And what are these the end-to-end components that are needed. Yes it can come in so it's just like normal as a component but just as react when you render something to your end-to-end ASS. So the ASS actually registers the component. In case of canvas the component you use. So I told you about the surface component. Surface component is the one which actually creates the canvas. Anything is rendered on that it's not rendered on the component. That single element is rendered on that. So if you check the code also you can see only one hand that encompasses our entire scene. And I don't know what's the name. So primitive component is supported by the canvas includes text images and what's amazing primitive component is it supports this view. So if you are using a normal application and you have a forest on the list or a vertical list a more common component is readily available. You just have to provide the data but you can do one thing which we need to do. So you can call if you want to use this functionality I am going to create it in a vacuum you can call that way with your application because that's what we do some of our individual features we don't develop it on the native application we don't have to do it on the web so that when you want to push up it you don't have to actually delete the web. You do that. What's the important part of your application? So is there a lack of this in your application that you actually should be able to use in machine? There is no such thing but I am a commentator so in order to use the same it was just the idea that we want to chunk it So that is again, they don't explode that in the labyrinth or in any other way. But suddenly they do not want to go through like, bringing labyrinths on the surface like, increase the level and all the same. This is one way to think about it. You cannot move in that direction. The other way also. Sending one more. Slashing people. Last question. What's it? Taking curve. You can't do it, huh?