European Centre of e-Commerce & Publishing


18/10/19
Web Developemnt - Web Services - Publishing - Web Design - e-Commerce - e-Publishing - e-Learning - Multimedia :: EUROCEC - Business Consulting - Web Development - Web Hosting - Domain Names - eCommerce - Multimedia :: Home










 


  

Build your Own e-Business

Our e-Business Suite of books for Web Developer’s Library


Read the book Register the book Pass the Online Exams for the book Get Your Own Professional Certification


Many people who think "e-Business" think "start-up company".
Either if you are an ongoing business or you want to create a new company in order to develop your own e-business applications, you have to follow a consensus and consistency web development methodology which will lead you to a global success strategy.

Our "Build Your Own e-Business" Suite of web development books has created based on Session Scripting Programming - SSP™ methodology in accordance to PHP Session Managment and MySQL. Thus, all our books have carefully planned and written following the PHP - SSP methodology, in order to cover all web professional requirments and to be read and absorbed over the course of one week (six days).

Many of questions which one web developer needs to ask to prepare an e-business development plan must be successfully answered, or at least put in the "I desided to implement this web developement methodology" be answered.

It's very important for web development books to teach not only theory and technquies in connection with their subjects but serious methodologies of web development as a gloabal business success which could lead wed sites and e-business applications dynamically to best performance and profits.

Thus, if a web development book has written based on methodology which does not make any reference about a sudden increase of total visits in an e-commerce site, is the one reason of the web server bottle neck problem. The other reason for the bad web server response time, is the database driven schema through which visitors browsing the web site.

In most of the cases in database driven sites, for each user's request before the Web server sends the specific document, a PHP script is exectuted in order to access the database and to make menus and drop down lists with the appropriate links for the site browsing. This causes serious time delay, because for each web page a new access to database has to be made for a new creation of menus and trop down lists.

A sudden increase of visitors in web sites like e-Learning or e-Reservations could drop the whole I/O procedure and the web application to collapse.
To increase the bandwidth is not the solution, because it does not reduce the delay time of the Web server response when it faces the bottle neck problem. Thus, we believe that the critical decision for that is to minimize the access I/O to the database for each user - visitor and according with it to reduce the Web Server Latency time.

Matters like these must be answered by web development books and from authors and publishers who respect their selves and their customers.

Our Session Scripting Programming - SSP™ methodology based on the following figure.

Our methodology we implement transmits the access database driven schema from Database server to Client Side using open source coding and PHP Session Management.

Look at the platform in which our SSP™ methodology model is based:

1. Web protocol HTTP and the HTML as the platform language
2. Windows or Unix/Linux as the operating system of the Web server
3. Apache open source software as Web Server
4. MySQL open source software as Database Server
5. PHP scripting open source software for SSP™ programming
6. XHTML, JavaScript, CSS and DOM for the Web browser programming

The PHP script that creates the session variables is executed only once, when the User's browser loads the home page document homepage.php after the successful user's log in.

During this procedure the PHP script accesses the database and takes the links (URLs) from the specific structured tables that they pass to the session variables. After that, while the User navigates the site we do not access the database again to create navigation menus and drop down lists. Instead of accecing home page again, we use an instance interface document for the home page.

In each level of the site structure it is obvious that we need to have a link, which will return the control to the home page. Thus when the User clicks on this link the browser will not load the homepage.php document but another clone php document that will be an instance of it, or an instance interface.

This instance clone interface document will have the same structure, the same presentation, the same contents like the homepage.php and will use the ready session variables to print out the navigation menus and drop down lists. But it will have no access databse code as well as this has made by the original homepage.php document. As you can see this design proposal minimizes the total access to the database Server per User' s session. The instance interface clone document homeinstance.php does not access the database because it uses session variables that are stored in the browser' s cache memory.
With the instance clone interface document we have achieved to transfer the database driven control for the site navigation from the web server to the Client side through the User's browser.

You can free download all source codes of this book which are available at w3opensource.org for our readers. Also, the book should provide you with a deeper understanding of how the different technology is involved in database applications and how they are applied in environments like the web. So, our Web Tutor learning and educating environment leads you to achieve a certified professional level of skills step by step.