.png)
.png)
.png)
AJAX and PHP, Building Responsive Web Applications : PDF bOOk
by
Cristian Darie
Bogdan Brinzarea
Filip Cherecheş-Toşa
Mihai Bucica
What You Need for This Book
To go through the examples of this book you need PHP 5, a web server, and a database server. We have tested the code under several environments, but mostly with the Apache 2 web server, and MySQL 4.1 and MySQL 5 databases.
You can choose, however, to use another web server, or another database product, in which case the procedures presented in the chapters might not be 100% accurate. It is important to have PHP 5 or newer, because we use some features, such as Object Oriented Programming support, which aren't available in older versions.
Please read Appendix A for more details about setting up your machine. If your machine already has the required software, you still need to read the final part of Appendix A, where you are instructed about creating a database that is used for the examples in this book.
 |
| Download |
.png)
AJAX and PHP, Building Modern Web Applications : PDF bOOk
.png)
AJAX and PHP, Building Modern Web Applications
by
Bogdan Brinzarea-Iamandi
Cristian Darie
Audra Hendrix
Building websites since 1990
Before getting into the details, let's take the inevitable history lesson to make sure
we've got our definitions straight. We promise we'll keep this short. If you're a web
development veteran, feel free to skip ahead to The world of AJAX section.
Although the history of the Internet is a bit longer, 1991 is the year when HyperText
Transfer Protocol (HTTP), still used to transfer data over the Internet, was invented.
In its initial versions, it didn't do much more than opening and closing connections.
The later versions of HTTP (Version 1.0 appeared in 1996 and Version 1.1 in 1999)
became the protocol that we all know and use.
|
| Download |
Securing AJAX Applications : PDF bOOk
.png)
by
Christopher Wells
HTTP Transactions
When Jim hooked up with the server using telnet he established a connection to the
server and began initiating an HTTP transaction. Next, he evoked the HTTP GET
command or method followed by the name of the resource that he wanted—in this
case, classic.html. This took the form of a specified Uniform Resource Identifier
(URI), which is a path that the server associates with the location of the desired
resource. Figure 1-1 shows an HTTP request.
|
| Download |
Subscribe to:
Posts (Atom)