 So this is Kashif. I do work here as a software engineer in Newstar. Sonya Star is the telecom company. They do work in the ISP and other telecom domains and they have other security services as well. And I came in touch with Delhi and then we discussed and then we set up this group in Washington area. So to educate or to communicate or to make a group to do some discussions around the technologies and then open sources and then NGO works. So non-profit things. So I came in with Delhi's help. I joined this group TechSoup to help community in the different sections on different area. So today we decided to start an event. So I thought what should be the first event? So I thought it would be good if we are going with the technology then we have to discuss with the WWW. Nowadays this is the baseline for the technology, right? Everything. If we have to go, we have to go to the browser and search and look for the information for the data for anything. So I thought it would be good to go with this topic first. So I picked the WWW. The history are the basic information. So let me go. Before that, like the TechSoup, as Ali mentioned, so yeah. So this is the non-profit group. So we started here and we are trying to build this community, a strong community in this area and Patrick, we will need your help on this one as I said, it would be good if you will work together on this section. Yeah. Okay. So we will build a stronger non-profit technology in of our tools. Okay. So let me go with the WWW history of what is actually World Wide Wave. Generally, we people used to know this one as a wave. But today's agenda, we will cover the introduction of wave, history of wave, the wave and the internet. What is the difference between wave and the internet? What is web servers? How we do? What types of web pages we do use? What type of site? How to deployment and hosting and managing our website? So let's go with the introduction of WWW. So the WWW is a worldwide wave commonly known as the wave is an information system where documents and the other resources are identified by the uniform resource locator and which may be interlinked and accessible over the internet. So we do have two things. One is a wave and the other one is the internet. So internet is, we can say, generally people use both term like internet and worldwide wave WWW together, like in the same meaning. But there's a basic like minor difference between the wave and the internet. In fact, if we can say the internet is the infrastructure that wave used to access their resources and to get this facilitated with the internet infrastructure. And the resource of the worldwide wave are transferred via the Hypertext Protocol like STTP. And we client use a wave browser like as a client application, wave browser, and it is published by a software application called a wave server. So if we talked about the internet or if we talked about the wave, so basic things we need the client application, the browser where people need to type the uniform locator, they have to type the address. And from there it routes, it use the internet resources to get the domain where it has to be go. And then we have a wave servers that is the destination of that we will discuss of different things like history of worldwide wave, the internet and the ways of how, what is the difference, basic difference between the wave and the internet because these two versus symbols each other and understanding of wave server, what is this server, how it's different types of website like the wave pages, what types, different types of wave contained and understanding of hosting and deployment of this website like how can we host or deploy our websites and any questions then. So let me start with the introduction of worldwide wave. So worldwide wave is most commonly known as a wave. So generally people used to say as a wave and it is the information system where documents and the other wave resources are identified by uniform resource locator, which may be interlinked by hyperlink and are accessible over the internet. So this is the Wikipedia definition of worldwide wave. So world of wave is like, you know, the spider wave, right, connected with one another and it's a complete mesh. So worldwide wave is, we can say as a repository, we do have all those contains and everything available. And we have to identify those information through the uniform resource locator. So generally we use to see other URLs, so uniform resource locator. And in the website, we can have a multiple resource locator. So each wave page can linked with the other wave page. And through that the interlink we can, we do access over the internet. So internet is not the wave. Wave is not the internet, but they do have a closed relationship. Wave is an application. Internet is an infrastructure that's provide support to work or to run the wave to the web application or website. The resource of the worldwide wave are transferred via the hypertext transfer protocol. We used to say as a HTTP maybe accessed by the users by a software application called a wave browser and published by a software application called a wave server. So for the website or for the web application, we do need a client application. We used to say as a browser like Chrome or Bing, we do have a Safari, Firefox, so different client browser. We do use and we do type the URL in uniform resource locator, the URLs in the website. And then we look for the some of the information over the internet through the wave. So internet is an infrastructure. They provide the support to run the web application, the website. So internet is the network of the system, networks of the computer, networks of the application servers. So this is the internet. They provide the basic infrastructure to the website. So if we are using, for example, I have used here, some site.com. So some site is the domain name and STTP is the protocol we are using to access the wave server. And this some site.com can be located on the other side of the world. Nobody knows where this domain is hosted, where the wave servers resides. But this intra, the internet, the network, the computer network, the internet actually provides the beauty of this to find this website from the any side of the world. Like it could be in Japan. This website can host it in a Japan or Australia or in Canada or US itself. So they find this address and get this information and load the page. So when the client, when the user type the URLs on the client, hit the submit button, it send the STTP get request and find the domain name and get the information and it load the first index page to the client interface on the client browser. But we do always have a question, right? How, how my web browser connected to the world, how many web browser find wave server? What is the page not found? What is the server not found? What is the IP address where it fits? What is DNS? What are those rules? How internet's work? So these are the questions we do. Like these are the curiosity we always want to know that how internet's work, how the web works. So before go to that, the function, before go to that, those answers, let me go back to the history and just know how this when this worldwide wave invented when people started using this worldwide wave. So I do have some weak information. So Sir Tim Berners Lee invented the worldwide wave in 1989. And Sir Tim Berners Lee is a British computer scientist. He was born in London and his parents were early computer scientists working on one of the earliest computers. So he had a family background of the computer computer. So he had some curiosity and based on that he invented something. So earlier Lee was working on the CERN. Yes, CERN. He was working in a European organization for the nuclear research and where he invented the worldwide wave. So actually Tim had written three fundamental technologies that remain the fundamental foundation of today's wave. The first was HTML, Hypertext Markup Language. This is the programming language for the, you can say for the wave, the baseline of the web. The second is URI, Uniform Resource Identifier. And we can, we generally use to say as an address, the web address. And third, the Hypertext Transfer Protocol. So this transfer protocol actually communicate from the client application to the server. And client application decode the HTML code in, in the, you know, interesting way interfaces or something. So it did translate this Hypertext language, Markup language in a readable form. And Tim also wrote the first wave page editor. So he, he, for, for that one, he wrote the application, the editor that was the WorldWiveWave.app. This was the first editor for the browser. And one of the interesting thing, like he's personal, he's the office machine, the office computer was used as a first wave server. So the first wave server. And by the end of 1990, the first wave page was served on the open, open internet. And in 1991, people outside of the CERN were invited to join the new wave community. So from since 1991, people are getting benefited from this wave. And this was the gift of Sir Tim Berner. And then Tim moved to CERN to a Massachusetts Institute of Technology in 1994. And he founded the WorldWiveWave community and the international community devoted to developing open wave standard. And he is the main, the director of the Blue C3 of this day. So this wave is the gift of Sir Tim Berner. So we cannot assume, like, how we should be, like, without the wave. This is one of the beautiful gifts to the technology. Any questions so far? Okay. So now the basic, the wave and the internet. The WorldWiveWave, commonly known as a wave, and internet enables resources on the WorldWiveWave. So internet is a networks of network. So we do have a network. It could be a LAN at home itself. We do have a network, right? We have one modem. We do use routers and different devices connected with this router. And we do communicate with each other with each devices. So we do have internet in our home itself. So we do have use internet or LAN, you can say the network, we do have a LAN at home. We do have a LAN in office. So all LANs are connected and through they do make, they do build a big network of this network, just called as an internet. It uses hardware and protocol to function. So router, so for this, if we have to build a LAN or network at home itself, we will need a one router and some devices to connect with that router. And we can access our devices, internet, like, we can access our home devices. And if we are in office, our office machines and systems are connected, printers and other devices connected with this router, and we can communicate from one machine to other machines, but we cannot communicate outside the world. We do communicate from within the LAN. But if all LANs are connected with the different router and modems, then we can do connect with the outside of the world and that is the internet. So the router connected to the internet is modem. The role of router is to keep traffic with inside the LAN, inside the network and outside the network. And modem is a device connected to the outside network that belongs to ISP. So let me, with this picture, so just assume this is one of the internet, like this is one of the network we do have at home or office. So we are connected with router and we do have a modem. Modem is actually the connection from the outside world. So ISP, if we do have some internet connection from the ISP service provider, they do provide modems and they do provide the external IPs in that modem. So once we do connect with the modem, without this modem, we can have the internet, internal network, we can have a LAN, we can communicate multiple machines within the LAN. But if we do have a modem and we connected with the ISP and ISP provided this modem, then we can connect with the ISP network. So now our network has expanded. So earlier we had just LAN, now we have ISP and ISP can have the multiple customer. So ISP is connected with the multiple. So now we do have a big network. So if we go through this modem, we can connect with any of the machine that is connected with this IP. And then these IPs are connected with the regional IPs. So these are the big IPs like they could be a smaller, they have a big regional IP. So multiple IP is connected with the big regional IP. So if IP is connected with big regional IPs, so my access has increased, right? I can connect through this modem to ISP. ISP, any of the machines connected with the IP and now I can access any of the machine that is connected with the regional IPs. So because every ISP has a modem and every modem has a public static public IP. So and all these regional IPs connected with the backbone networks, these are the big companies, they have the access in multiple cities or countries. So they connected with the backbone network. So if my website is hosted on the other side of the world and I'm trying to access some of the website from here, so it based on the host name or let me take here as IP. If we do have IP, my router will decide whether it has to be internet, internal network or outside. Then based on that, my modem send it to external and then they find for, they look for my IP address or the domain name and then finally they find the destinations and once they do reach the destinations, they return, they return reply 200 with that the web page, web content and again it come back to my machines. Then I can see the website is open or my whatever I'm looking for that. I do see on my browser or my client application. So as I mentioned like ISP has its own network, ISP also connected with outside networks, ISP's router, route traffic within the ISP network or outside of the network where ISP belongs to. It could be a larger ISP or regional ISP. So regional ISP is connected with the larger network and there are the companies that operates network in the multiple cities. Those are the backbone of the network, they connected with different cities and countries and router find the base route to reach the resource which we're trying to reach through the WW. So if I'm coming back to this picture, so I'm here, my website is hosted in some of the web server. We do have a complete world over here and my internet actually helps our webs to find the destination web server and get the page load on the client browser. So this was about the internet, how internet works, not the DNS because here we generally say like with the domain name, we say the name like xyz.com, google.com. We do not say the IPs, right? But here our networks, we work on the IPs and if you see like we do have two types of IPs, IP version 4 and IP version 6 and it's still like now this IP version 4 has some limitation. They had a some limit count because it works on the octet of class base, right? So every IP should be unique because IP is the name of the machine. If I do have a machine, there should, if someone has to identify my machine, they will based on the IP, right? So IP is the unique, we cannot use the duplicate IP for the different machine like same IP for the different machine, we cannot use the duplicate IP. So IP should be unique and now we do have many iOS internet devices and every device need IP to identify for their identification. So it is the complete range of IP 4 is almost exhausted but still we are using IP 4 and IP 6 has 128 bytes. So they have the extended range. So IP 4 was the class base and these works on the protocols. So HTTP, we talked, right? So for HTTP, the Hypertext Transfer Protocol, now browser use this HTTP to send message to the web server and this runs on a port 80, like by default it is port 80 and if we do use the secure transfer protocol, HTTP, so it runs on a 443. And for the internet communication, this works on the TCP and IP. So two things, right? Both works together. On the machine, we do have a TCP that if we do have to communicate from this machine to web server, right? So we have to, we need our own channel for the communication. So IP is to use to find the web server, use to find the destination address, IP use over the network and TCP is like the transmission control protocol. It actually fragmented this message into 1500 KBs, 1500 bytes, I think it's KBs and they divide the messages in a smaller chunk and then they put some header, like if we do submit requests from this client. So this client TCP put the header of the source IP address, the destination IP address and they do have some sequencing. So once it goes and reads to the destination, then destination knows that what was the source IP address and based on that the destination return and it reads to the source IP address. So in TCP IP protocol methodology, we do send the header IP address, request IP and the source IP and destination IP address in the headers and through that it communicates from source to destination machines and then come back to the source machine. Any questions on this one? Any? Just a quick clarifying question. So why does TCP break it down in terms of different component parts? Is that to speed up the transfer process? Like what's the reason for breaking it out? Right. So they do make small pieces and small pieces communicate independently without like, if let's take an example, I do have one message and it's broken into two parts. TCP broke into parts. So message A can go to the one route, message B go to the another route. So it is the faster as for the security as well. If someone will encrypt and decode one of the part, if they will not have the another part, they cannot use the complete message. So this is for security as well. So once we do receive, so our the client, the TCP on the machine, once TCP received all those messages, then it sequenced it and displayed to the client browser. And same on the server side, they do decode and they, if any of the package is lost, they do recent application, that packet again to the server or to the source or to the destination, but they break it for the faster. And it is not sure like it is, it is not like all packet will follow the same route. Two packets can follow the different route. And even the, if a message sent from client to server, it is not like the same server will send response on the same route. Server can use the different route to send responses to the client. So it is, it is totally algorithm based on and it is not a fix like say they will all packet will use the same route or for same route for incoming or ordering. It will, it always, it always vary. Am I right, right in remembering that this had something to do with the, this architecture has to do with like the military origins of some of the internet where they're like, oh, if one of our locations has been blown up, we need to have another way for the data to automatically reroute around. Right, right, right. So that's why like, and for that one as well, right? Every, every packet will have is encoded and they are broken down in a different package. If any of the package is like, you can say like lost or decrypt or someone hacked that one, but they will not have the complete information. Got it. Okay. Anything? Okay. So, so now the DNS. So DNS is the domain name server because here we, on the network, we were talking about the IPs and IPs are unique, but here on, if we say on the website, we never use IPs, right? We, like, we never use IP on the front and we, we don't say like, this is my IP, go and check on the website on, on, on the web or client. We always provide the domain name. So there should be some mapping, right, between IP to domain name. So we do have this, we do like, we do, we have a DNS servers all the way and DNS server actually DNS server is nothing, just a map between the IP and the host name. So if in the same example, this is the client browser. And if we have like some site.com, and this is not the IP, this is the domain name. If we send it, then it goes through this modem to ISP, right? And ISP to the regional ISP and regional ISP has a domain name server. So they do have a mapping, like what should be the IP? Did they find this DNS or not? If they do not find this, if they, if they do find DNS within their network, they just respond like they got it, they find this web server, right? If they do not find the DNS within their network, then they send it to the other network, the backbone network, like they are looking for this host name, do you know the address of this host name? If this, the DNS server find those address, they return it. If they do not find that the DNS address, they again transfer to the another. So through this mechanism, they do such the DNS name in the all DNS servers. If they do find the server, then they just reply with the content of that the website because DNS server gets the IP address and based on the IP address, they do route to the appropriate web server. If they do not find the DNS information, they do not find the IP address, then they do return 404, not found. So for this example, some site.com custom end user requested from here, it went to this regional IP, they didn't find DNS. They don't have any DNS entry. And then it went to the backbone network and backbone network had multiple DNS server where they didn't find. Then again, they have the another backbone and then one of the DNS server has this entry like this was the website and this is the IP address and this is a public IP. So once they found the public IP, then it from this DNS server routed this traffic to this IP. Now the traffic is going with the IP. So they routed this traffic, this request to 190.233 to 10255. And from here, it reached to the web server. Now web server has both source IP and destination IP. So now they will take a different route. Once web server has this request, the web server will return 200 receive successfully. And then the request they will have a get request. So they will post the content of the index page and web server has a destination as well. So they will send this response to the client browser. So client browser will receive this response. So during that response, they do have IP. Then it will not come through the DNS servers because they do have IP. But during that the request initiation, they don't have an IP address, then they need a DNS server to get the mapping of this domain name versus their IP address. So anything on the DNS side? So the understanding of the web server. So now we have discussed about what is web? Why does internet? Why does DNS, right? Now what is web server? So because here the destination is web server, right? If we if we are looking for any of the website or any of the URL, it needs to reach to the web server. So what actually web server is? So web server is a combination of hardware and software. Like generally people used to say that hardware and software, but is hardware is like, we need a hardware for anything, right? But basically it is a software and software known as a STTP because it's run on a STTP protocol and STTP is runs on a port 80 and the all web site or web applications work on the STTP protocol. So sometimes we use to say as a STTP protocol or this is a web server. The application runs on a hardware that provides the processing memory and storage. So for any of the software will need a hardware. So sometimes people use to refer as a hardware as well because we need to install this software application, the web application somewhere that's needed storage processing memory. So primary function of web server is to store process and deliver web pages to client. Default port is 80 and secure. Like if we do have a secure SSL certificate, if we want to do the traffic through the secure channel in the encryption mode, then we need a secure certificate and it runs on 443. So we generally used to see on the STTP, it's as a STTP S. So if we do have a S, if we do have a S here, that means it is a secure channel, it's run on a 443. So if we say web server, so the function of web server is to store. So if we say store, like we do have a web application. So web application contains some of the files, right? We can upload, we can download and we do have a web site itself over there. So we need a storage to store all those files process. So if we do have a request, right? So based on the request, different type of request, we have to process web server has to process it and return the appropriate content to the client. So they have to process and deliver web pages to client. So if once they have that the process, they have file, they have processed it, not they have to deliver, they are responsible it to deliver those content to the client as well. So these are the primary function of the any of the web server. They need some storage. They have, they need some processing and they have to deliver a message that they have to run on the protocols. Okay, so any question on web server? The question I have is related to the secure port, the 443 in the SSL. So when you're using a secure channel like HTTPS, when you're adding SSL, is it essentially encrypting the transfer of the information from the client to the server? Is that how it works? Right, right. So when we do use secure certificate, then we have to buy the certificate and we have to install on a web server. So on the web server will have that the certificate, right, they have the algorithm for the encryption. So once client submits request with 443, so that means this is a secure channel. And sometimes client browser also need to install the certifications, like if we do have, but if we have 443, so that means this is a secure channel. So whenever the request raised to the server, server request encrypted and like two ways. Normal, they do communication between the client and server openly without any secure tunnel they do on the plain text. Just take an example, they do have a plain text, but with the 443, they do use the encryption. So client will also have that the encryption algorithm. So because they do return, right? So they do send some keys. So the communication between the clients are client and server is encrypted. So if someone will hack, someone will get that the data, but they will not have that the key to decrypt. So they will, there will be no use of getting those pages. If some intruder or someone face that those information. So SS 443, like the SSL is the secure channel, they always go through the encryption. They don't have a plain text. So if I said, if I have to send a message, hi, how are you? So if I will send it to port 80, it will go as a hi, how are you? If someone will encrypt, even it is an intruder will get it. So they, they know that it is how or how are you, right? But if I will use the 443, it will be encrypted format. So if someone will get any of the packet TCP packet, they will not decrypt it. So they will, there will be no use for them. Okay. Okay. So, so now we, we, we, we understand, like we discussed about the, what is wave, what is internet, what is wave server, what protocol we do use, right? So now we do have a wave server. So how, what type of websites on how, like what types of website or wave application generally we do have. So generally we do have a two type of wave content, either static and dynamic. So the basic difference between static and dynamic as the name says static, that means static. If we have something written on my, the HTML file, and if we have uploaded my HTML file on the web server, if 10 different user is opening, they will see the same page, right? And if I have to update any of the information in my web page, then again, I have to go with the same process. I have to download, or I have to edit that my HTML file on the web server. And then I, or you can say like, I have to download and I have to edit it and then upload back to the server. And then it will display on the website. So static on the runtime, we cannot change any of the content of the web page. That will remain same. And for every user on the world, it is not like the user specific information we can display. So static page is like, is the same is ungenerally HTML site or use for the static page. Dynamic content is like we do have the, you can say the information on the wave page is not the same for all user. If you are logged in with your profile, you can see your content on the website. If I'm logged in with my user profile, I can see my content on the website. Or the other example, if we have a shopping cart, right? And if we are dealing, if we have merchandising something on the website, and I have five product to sell, if my page is static, then I have provided only five information. Now I have a six product to launch, right? So in this case, I have to update my new information on the website again. So that will be the complete process, download, update information on the wave page. Even if I have to change the price or address or telephone number, I have to go there, download and update the programming files or HTML file on the server. But in the dynamic content, I can add it. So for the dynamic, not just a wave application, not just a wave, HTML file will need a database. So the way servers have all those programming files, or you can say the wave pages, and that connected with the database as well. So if we do change any information in the database, application or website read content from the database and display to the user. So the benefit of this website is we don't need to go and deploy the same website again and again for any of the minor changes. We can update information in database and that will reflect on the website. So dynamic content can change on the runtime. If we don't need to, we will not have any downtime. Website is up. We do have updated information in database and it will reflect on the, so dynamic. And we do use, for dynamic website, we need to use some of the programming languages like Java, PHP, Perl, Python, .NET, and we will need a database as well. Like we do have a SQL, MySQL, Rackle, a different database. But for the dynamic content, we also need our admin or dashboard or admin portal where we can update data in database itself. So this is the basic difference between static and dynamic wave content. Any question? No. So understanding of hosting and deployment of website. So for any of the website, we do need basic, I think, first to register our domain. So we do have a few registrar, domain registrar companies, they do registration, and they do provide host. Some companies, there's both hosting as well as registration, but some just do the registration. So, so major, we do have a go-day, go-daddy, HostGator, Google Domains, and other service provided, they do registration. So if, let's take an example, I have to set up my website, xyz.com, right? So first, I have to register my domain name. First, we have to check, is it available or not? So every domain company provides some tools, so where we can check the availability of that domain. So if my domain is available, if I'm looking for xyz.com, and if it is available, so I can go to any of the registrar company and register my domain. So if I'll register my domain, so that means they will like now, I can use that domain name for my application, but just registration is not the complete setup of the website. This is the first step to get the domain name. So once the domain name is there, then I have to select our Wave Hosting Company. So Wave Hosting Company and the domain registration and Wave Hosting, they do have these we use as services and this is like the have to do the renewal every year on based on the different plan, but these are the continuous thing we have. It is not like one thing. One time we have registered our domain and it's done. We have to do the renewal or we have to pay every year for that the domain name and for the hosting. And Wave Hosting is like we are renting something, right? So now we have the domain, but we have to host somewhere. We need some infrastructure where we can put our files. We can put our videos and audios and our information and we will need a bandwidth to access those files. So for that one, we need a Wave Hosting, Wave Hosting Company. We need a service provider from the Wave Hosting to host our website. So the basic domain registration and then Wave Hosting. So while choosing the Wave Hosting Company, we have to see what is our requirement because we do have a Linux server, Windows server and hosting companies do provide Wave servers on the both operating system. So based on our requirement like .NET, if we have any of, if my plans to use the .NET application for my website, then I have to pick the window machine, not the Linux server. If I want to go with the PHP or Python or Perler Ruby, so I can use any of the window or Linux servers. So I have to see which one is useful for us. Second, if I don't want to write any of the Wave site from the scratch or anything, I just want to use on the shelf application and just customize and just do the content management and just put our content, not the complete development of it. So we can use some open source CMS available like WordPress, Joomla, Drupal, Django. We do have many CMS applications. So you just have to install these applications on your Wave server and it is ready to go. You just have to put your content based on your content, based on your choices, you just have to put your content. So these are the ready to go applications. You don't have to do a Wave design or Wave creation from the scratch. But if you go with the programming language, then generally for the static Wave pages, just HTML is fine. But if we have to go with the dynamic then Java, Perl, PHP, .NET, Ruby, Python, so we do have our different programming language we do use. And we need a Wave hosting, Wave servers, Wave hosting companies for the storage. Like if we have to host our application, Wave site, so we will, Wave site that means we'll have some files. So we have to hold those files. We need storage. We need processing capacity because what will happen if 100 or 1000 user will log in or will access my browser, Wave application almost at the same time then what will be the response. So we have to see the processing and bandwidth as well. We have to see the server memory to see how my application will respond if we'll have, if multiple users will open my Wave site on the peak time or off peak time. Nowadays, we do have a cloud. So based on that, we do have elastic things. So based on the requirement and based on the high peak time or low peak time, they develop a bandwidth and all those things. But yes, these are the basic things we do need for the hosting. So once we do have registration, like once we have a domain, once we have the, we have a, we, like we allocate, we bought some space from the Wave hosting, then the domain register, then Wave hosting provider provides C panels. So they do provide some panels to us. And for the domain registrar also provide some configuration panels. So what we have to do once we do have a domain registration, we do have a hosting, then hosting companies provide the domains, our name, DNS names or IP address, right? So in the control panel, we have to configure, we have to point those domain names and we have to configure the DNS name in the C panel of the domain registration. And we have to point like now we have the domain, we have the hosting company IP address. So we have to configure all those information in control panel. And once it is ready, it takes almost 12 to 24 hours to get this configuration live across the internet. So it takes like 12 to 24 hours to get live, website up or website live. And once we do all those configuration, it is ready to go. So these we think we have to consider a few things while hosting our website or while starting our website, like the web server, we have to pick what programming language or based on the requirement, we can choose what application or programming language use and where we have to host what should be the capacity bandwidth. Because for the bandwidth, I'm just giving you one example. If you have a page of 2kb, right, the index page or welcome page of 2kb, if the client is requesting for that page, so they are going to use a 2kb file, right? So they are consuming the 2kb bandwidth. So if 100 user is logging on the almost at the same time, right? So it will be a 2 into 200 kb, right? So bandwidth is required because if if we'll use the list bandwidth, then what will happen if more user will try to access the page almost at the same time, then then other page might not render on their client, because if they will exceed their bandwidth, their capacity. So for that one, we will need and we'll need the bandwidth and the processing capacity. Okay, so any question? No, that was really helpful. So almost done. So any question, overall question for this one? I know like I have more, like actually right now I don't have any C panels, that's why I didn't provide any of the screenshots, but if I have any then it would be good to provide some of the screenshot for the C panels that would be really helpful. But yeah. No, I don't have any other questions. This was really helpful. Like I really appreciate the kind of broad overview. What was especially helpful for me anyway was the review of the transmission and the transfer protocols with HTTP and going from place to place. I sometimes have a hard time visualizing all of that. So I appreciate that. Thank you. Thank you. Thank you. That was a great first event and I guess, yeah, this would be a great time to start bringing in other talent. We may have successfully twisted Patrick's arm while you were off camera for a little bit into doing something maybe around training people. I didn't realize actually and then I thought what is going on then and then and then I know like it was not working at all. That's okay. So I'm going to dive into my next call, but congratulations. I'll get the video up to you by the end of the day. And yeah, and I would encourage you and Patrick to talk and see if maybe there's a future presentation or interview you do with him around like onboarding, training, bringing people into new platforms that could be quite interesting for a future event. But I'm off. Ciao ciao. Catch you soon. Thanks much Eli. Yeah, so thanks so much for the walkthrough. I appreciate it. And yeah, I think I would be interested in seeing what we might be able to do for future events. Let me actually in the chat here, I'll put my work email and feel free to reach out and let me also give you my LinkedIn profile as well. There you go. Yeah, I'd love to stay connected since we're kind of neighbors. Love to see what we might be able to do. Moving forward for sure. Sure, sure, Patrick. And I have planned for other two events, but like earlier I had planned for the December last week, but you know, the Christmas week, so I extended that one. So I do have two more events, so I will do mostly on the January end of January and end of February. And in the meantime, I think before that as well, we will be in touch and we will make a new plan for something in this area to some new events or anything. And if you'll have any input, please let me know.