 Arwi sabOGd de gosam sït fiquem in shogam, oki, le titolo e Goi ngrestful OK, pake goi ngrestful Goi ngre наг女 The restful is explained quite well if we take into account the title of the rest API. To move, to go in, because I want to explain how we should move from the old Ajax Endpoint to a more modern solution. This is so new, and when we went in the day of rest two years ago, there was a new one. Today no more, we have a very natural product, so we can go in the restful. Okay, now practically I have already recorded all the content of this slide, because my introduction is the only thing that I have added. Today I have made a longer slot, so there is a lot of possibility to make mistakes in every type of recording, so it is probably fun to do this part. Okay, the code that I use, I will show you some codes. I am in a repository, there are three branches. The first is Ajax Endpoint, which is practically our potential situation. Second, when we have done the step towards the rest API, we still use this Ajax Pula technique, and then in the end something that is presented a little more restful. And if you put it the following check out, and check out these people, a code that is simple and legible. And also if you know Martin Fowler, he is the most important person in the programming project, he said that good programmers write codes for humans. And different legible codes, according to me there is also someone who may not have a positive experience in programming. My approach. Okay, let's start with Ajax, I have already said Ajax many times. In the other slide I have the idea of using a Batzboard Bingo, because if you use a positive word, a positive word, a positive word, because you know what I really want to say, that in the end we make a game, we put all these words on a map, and then in the end someone says Bingo, because I have managed to do five things very well. So a couple of these things are also important, and maybe Ajax and the part, as in chrona di JavaScript, and XML, which is already quite important, which is a concept that explains a bit everything. XML in this context is a historical thing, but in the end, Ajax can still use it in this way. And in the end, dynamic content, and we are not interested in it at all, in all cases, because they are very important. Okay, we have this translation of Ajax as in chrona di JavaScript and XML. And let's go on. I have told a story, when I started writing the HTML and now I am old, the content was sent to a request server and returned to the page. And if you want something dynamic, you can click on a link and make a reload of the page. And so this user experience was quite bad. And let's talk about the final year of 1988, when Microsoft and this part was fun, maybe I started to do research for the project of Outlook. And then I went on, especially Google, put a lot of effort in this project. And so far, we managed to have in 2000, 2005, 2006 something like a little more concrete of a standard base. And there you have to say that finally we have something concrete in this sign here, it is written on the first article, on Ajax and I think it is written in 2005. Ok. Ok, there is no point. Ok, we always hear Ajax, but in the end we do not understand as much as the flow of this thing. I said that before, we made a request to the server and returned to the page. Now we have a presentation which is called it's an HTTP request in the page just downloaded, made a call to another business logic that for this work we made a content that we can use to create a more dynamic user experience. Let's go to our wordpress solution. I think when we want to use the JavaScript in our solution we use a hook that in the end does only one thing. We say also that take this file.js and put a queue and then when we need a page we want to find it inside it is right. In this case we put a couple of variables because maybe not everything is necessary but in the end we have this thing in the end just for the translation of dynamic contents we put the Ajax inside so we can give our page an endpoint then we have this JavaScript because I think at least we all know how to read we know how to do with JavaScript in this file that here in my demonstration each click in a page makes this code go away. In this case we find our object called lmc.ajaxol and we transmit data towards this Ajax of jQuery the interesting part in this case is this variable action which is very important because when we want to work as a request we want to transmit Ajax towards the BKP there are two actions vp.ajax anasco vp.ajax anasco note this part is important for users who are not logged so usually you always find two programs that make you understand that the concept is a bit wrong because in the end for example you see two times for a function that is used in this file because there is a layer that you can manage for the authorization for example because it is very hard I think then we have a function available as a request for jason success or error and there is nothing else to create a jason a sample out and then we have another for example ok let's talk about api because we have called the rest api in the end and api is especially important to talk about programs or code one to the other because it is important an api you might have an api and to read the user to make an action on the site without having to leave the site for this type of action because if you use ajax and if you use another api you might have in the first page inside all the necessary actions and then api today if you see api api there are parts around so you can buy if you are free you can integrate so this part is interesting to get pages or all the user experience in general and then this this microsoft that you feel very often and in the end you have the possibility that you don't have an overhead huge or you think maybe a page that is very very graphic inside a lot of action a lot of innovation with the web user and as this application in the interface api let's go with that jason api if we put inside after our site slash vp jason we have probably all this this call that we see a little the op of the rest api I have used a jason beautifier a plugin pergrosa that the op a little more because otherwise it is a test that it is difficult to read so it is already a little and there are already a series of WordPress core endpoints that are already available then inside I believe also a plugin just in this case also it is very very ok and so you can also translate the rest of the directory then and see what is inside all these endpoints it is always interesting to squeeze a little ok after to be code remembered of the first part of the of the of the of the of the of the of the of the of the of the of the that the the of the the the and at point the of the but fatonado un woopi rest-response-object-van-organic-success. Okay, rest. Day of rest. Rest-a. Rest-a-na-to-a-ko-a-se, no? E una quasi-standard, non-e-propio-a-standard, as directed-ritch-bê-la-trav-est-a-l a-kia-bea-y rows-viest-o. E o m-m-m-j-e-s-e-m-m-l-e-s-e-m-r d-e-s-e-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-ma-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m. మాిలు మాలోస్రండి. మారడి ఎండి దిడి. లారినె పి లుని. మారు నీని కాలవ఩కి. మారునే మా ని పిలూచి. మారిలు మారుని మాని. In this case, there is an evolution in our GES, we add this type, I have done it also, there are also shots for this J. Curry Ajax, J. Curry Gett, etc. But I wanted to underline that you use these types, and then finally talk to someone else, and then I have already written in this case, to show you what to do with the rest of the ETI, but it is not necessary that you already write, because it is such a program, we can also call the CURR, because we have used CURST, but we have other programs that can be spoken with our WEST server. Okay, because I have to use the rest of the ETI. So, you understand that it is not so honorable to use this ETI, it is not easy to make a move towards this solution. Then, in my opinion, also the centralization of this solution under a WPJ, where you see what your output is, also why. Then for this, also a replacement for this old ETI, a J. Curry Ajax PHP, which probably makes a lot of effort. There are, as we have seen before, a couple of interesting extensions that help us, and then, let's talk about mobile apps, these things, they are becoming more important, you can make a step back and give a little more freedom to all these applications that come to us with Vue.js, React, all these things, that are very interesting. And maybe let's talk about things like performance. I remember when I went with Christian at this conference, we talked a lot about performance, we went to the WPJ, and so on and so forth. This is no longer true. This is no longer true. We also have Cloudflare, like Cache, that we can use, for example, if we don't really need it. But in reality, we spread a series of things if we use the WPJ, not even Ajax. Because when we make a normal Ajax, we create a series of things that often do administrative things, like plug-in apps, stages, all these things. And for me, it turns out that if we don't have 15% of performance, we use only the reset, instead of the first Ajax. Okay. And then security. There are a number of people or a number of people who are also complaining about security. Everything is open, now they can see what they are spreading, etc. This, for me, I don't understand it so well, because you spread data in common in every case, even if you are then packaged in an HTML, so the difference is really little. And then, as I said before, if you are centralized, maybe you can also install a plugin that manages JVT or any authentication, for you, if you really start the vision you close it. And this, I remember that our devops, once, closed the API because they thought it would be a risk. Nothing has worked anymore, and there is also a surprise that JOSP, for example, who already uses a REST API, if you close this thing, in the scene, things can't work anymore, things are more normal. Obviously, you have the chance to ignore all this, but let's say that the REST API now is a bit out of the fire of once, once the topic of the day and everyone spoke about the REST API and so on. Nothing concrete, so I hope that I have added something a bit concrete. But now we talk about Gutenberg and Gutenberg without the REST API is not even so nice, so it is a thing that is something else, so the road is a bit smaller. And then we have done this shift of road press, block versus CMS. And now we have done this shift of CMS for an application server. And this gives us so much opportunity when you are a developer, you become a type of backend developer, so it is good if you are in form of a function of certain things, of certain concepts, as a front-end developer you are more free, you can use VJS, React and everything that you talk about for projects and a bit more love. And yes, I have arrived at the end of my speech. I am a bit faster than before, but thank you very much. Thank you, thank you Dennis.