 So here's a checklist of tools and resources which you need to have your wonderful web-based database applications. And those tools and resources have already been discussed in detail in the prior modules. So you have sufficient knowledge and understanding to make that selection. Now there is a kind of a contradiction over here that you have to make that selection sequentially also and simultaneously also. And that will have a profound impact on the future of your web-based database application. Profound impact, remember because once you make those selections it would be difficult and expensive and painful to disassociate those things, to undo them. And the good thing of course is that it has to be done only once. So we have spoken about in a lot of detail about the ISP, about the web server, application server, about the database, about the FTP, about the email which we will be covering in this module. So I will be addressing these things from a point of view of making the selection and their profound impact on the future of your application. So that is the point. So I would again suggest you to look at the notes, read the notes, read the textbooks and raise the queries. So ISP and the web server now selecting hardware, software and the ISP. Now remember one thing that usually it is not your choice to make a selection of the hardware and software. Whatever the ISP offers you go with it unless you are spending a lot of money depending upon the scope and the nature of your organization and you are making that selection. Of course then you can do all of those things. Database must be compatible with the web server used. For example, you have to, if your backend database is malice short access, you have to ensure that this database is going to run on which operating system. It's not that you develop your application and when you are going to host it, it doesn't support. The operating system doesn't support it. Compatibility with the application server if run on the web server. They have to be compatible otherwise it will not run. The things which are running at your end they have to run when you host them also and I have spoken in lot of detail about the benefits of the type of domain name and the domain itself which you know. Now the point over here is that you should get your domain name because your domain name stays with you. Why because if you change your ISP that and you are using the domain name provided by the ISP it changes or if you don't change the ISP but the ISP makes configuration changes then your domain name may change and it would result in expensive reprinting of stationary, stationary, your letter pairs, your visiting cards and other stuff of course you can do it quickly on your website but the hardware things they will cost money, they will take time. So get your domain name. About the application server interface between the web server and your database. I have shown you all those diagrams which you can consult with them. So it is very critical. And it has to be compatible with everything. Now if you make this choice once and you need to move your application to somewhere else and they are not compatible then you are in a problem. Or say for example you have made this choice and you make a change in your database and it is not supported you have a problem. So you have to port things which is expensive and painful. Carefully select package including the database and the application server. You have to ensure their compatibility. You have to think ahead. You have to think ahead that what could happen. So this module is prompting you to think about those future scenarios. About the database, transportability of the database. That database should be transportable. The definition of the database should be transportable because defining the database takes a lot of time, effort, energy and resources. That for example about the scripts and the processes they can be defined. But defining the database takes time and effort. So ensure that if you have to make a change you have that database which can be transportable. Redesign database more difficult than rewriting the script. That point I have already made. Now you are working in an organization you go there and it may so happen in many cases that they have a standard database for reasons of their own and every application has to follow their database. Now what I am suggesting is that you keep in mind of a database other than that main standard database. You have to think about it that maybe tomorrow if certain scenario occurs what would be the second database other than the standard one. So look ahead. Now web authoring tools you have to look at the package also which is offered which can be offered by your ISP. But one thing is for sure that it is kind of a reverse of what we have discussed before because the output the outcome of web authoring tool it can be text editor. It could be WordPress or it could be other application or tool is HTML. Now HTML is a standard. So all those web authoring tools will produce HTML which is going to be hosted which will be running on your web server. And remember that there in an organization itself there will be a diversity in the browsers used by the same people in an organization. They can be different browsers and even there can be a difference in the version of the browsers. So you have to be when we discussed a JavaScript in the prior module I mentioned that people may have enabled it or disabled it and what are the browsers they are supporting it or not. So you have to take all of this into consideration. Authoring tool produce the same material. So it may be feasible. It may be economical that instead of buying an authoring tool investing in an authoring tool and learning it you engage people who develop that website for you. Now finally the file transfer protocol you have to upload your scripts your data your tables into your website for which you need a certain tool which is the FTP the file transfer protocol to update populated website. Now there are certain limitations of the integrated FTP which comes with your package because that may not allow you to selectively place the data to populate certain things. It may only allow you to upload files in a certain directory in a certain location. That is a big limitation because you have to have a hierarchy of file structures of directory structures where you upload your data and material for number of reasons which we will be discussing in the subsequent modules also. So this integrated files FTP have these limitations because they will intuitively load. So you have to be working if it is simple website is fine. You intuitively load into a certain file directory structure and not beyond that. Now finally email may not come as a default however certain organizations certain ISPs or certain database service providers offer email which is domain specific that domain could be of that ISP which I strongly recommend not to use use your own domain or sometimes they may offer domain of a third party for your email which again is a problem in my experience it was not working with that certain ISP. And so you have to go take additional step with regard to that email and that email may not come bundled and there is automated email also something happens you get an email. So there has to be a filtering mechanism of working with those emails so that they go into certain folders of your hosting solution. So that is all I have for this module thank you very much.