That's especially important if the client is not a user but a search engine crawler - it always helps if it sees what the user would see (even though, that's of course not your personal profile page - but the same concept applies to other pages, too).Īnother advantage is, that all logic happens on the server, hence the client's machine really only needs to render the HTML code. The advantage of this approach is that the client (browser) receives the finished website with all the data that belongs to it. In case you're interested: Our complete Node.js course does not only teach Node from A - Z, it also includes a section on templating engines and how to render dynamic web pages. These extensions are also referred to as "templating engines". The server-side language then used all that information to generate dynamic HTML code which was sent back in the response the browser awaited.įor this, server-side languages like Node.js could be used - typically in conjunction with specific extensions that make the dynamic creation of HTML code easier. The incoming request was handled by the server as instructed by the language used there. This means that the HTML code was dynamically generated on the server, by the server-side language used there. Still, if you inspect the HTML source code of that page, you'll find your personal data in there. Obviously, Amazon does not hand-write the HTML code for that page. It includes personal data like your name and order history. And with "website", I of course mean the HTML code, including the information which styles and scripts to attach.Ĭonsider your user profile on. It simply means that the website you're viewing is dynamically created on the server. It's not a reserved term or anything like that. Netflix, Twitter) are embracing these newer approaches.īut let's take a step back: What are "Dynamic websites"? It actually still is, but Static Pages and Single Page Applications are now rapidly growing and taking significant shares of the overall "website market".Įspecially modern websites and webservices (e.g. Go back in time by ten years and this was the most common approach.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |