<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Read all</title>
	<link>http://readall.org</link>
	<description>Read all about web developing</description>
	<pubDate>Wed, 02 Apr 2008 08:55:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<item>
		<title>Web development</title>
		<link>http://readall.org/2008/04/02/web-development/</link>
		<comments>http://readall.org/2008/04/02/web-development/#comments</comments>
		<pubDate>Wed, 02 Apr 2008 08:55:29 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP]]></category>

		<category><![CDATA[development]]></category>

		<category><![CDATA[Web]]></category>

		<category><![CDATA[WYSIWYG]]></category>

		<guid isPermaLink="false">http://readall.org/2008/04/02/web-development/</guid>
		<description><![CDATA[Web development is a broad term for any activities related to developing a web site for the World Wide Web or an intranet. This can include e-commerce business development, web design, web content development, client-side/server-side coding, and web server configuration. However, among web professionals, &#8220;web development&#8221; usually refers only to the non-design aspects of building [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Web development</strong> is a broad term for any activities related to developing a web site for the World Wide Web or an intranet. This can include e-commerce business development, web design, web content development, client-side/server-side coding, and web server configuration. However, among web professionals, &#8220;web development&#8221; usually refers only to the non-design aspects of building web sites, e.g. writing markup and coding. Web development can range from developing the simplest static single page of plain text to the most complex web-based internet applications, electronic businesses, or social network services.</p>
<p>For larger businesses and organizations, web development teams can consist of hundreds of people (web developers). Smaller organizations may only require a single permanent or contracting webmaster, or secondary assignment to related job positions such as a graphic designer and/or Information systems technician. Web development may be a collaborative effort between departments rather than the domain of a designated department.<br />
 <a href="http://readall.org/2008/04/02/web-development/#more-27" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/04/02/web-development/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Welcome to CodeIgniter</title>
		<link>http://readall.org/2008/03/17/welcome-to-codeigniter/</link>
		<comments>http://readall.org/2008/03/17/welcome-to-codeigniter/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 09:19:37 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP]]></category>

		<category><![CDATA[CodeIgniter]]></category>

		<category><![CDATA[framework]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/17/welcome-to-codeigniter/</guid>
		<description><![CDATA[
CodeIgniter is a powerful PHP framework with a very small footprint, built for PHP coders who need a simple and elegant toolkit to create full-featured web applications. If you&#8217;re a developer who lives in the real world of shared hosting accounts and clients with deadlines, and if you&#8217;re tired of ponderously large and thoroughly undocumented [...]]]></description>
			<content:encoded><![CDATA[<p ALIGN="center"><img ALIGN="middle" HEIGHT="164" WIDTH="150" BORDER="0" ALT="Code igniter" SRC="http://readall.org/ci.jpg" /></p>
<p ALIGN="left">CodeIgniter is a powerful PHP framework with a very small footprint, built for PHP coders who need a simple and elegant toolkit to create full-featured web applications. If you&#8217;re a developer who lives in the real world of shared hosting accounts and clients with deadlines, and if you&#8217;re tired of ponderously large and thoroughly undocumented frameworks<br />
CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.</p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/17/welcome-to-codeigniter/feed/</wfw:commentRss>
		</item>
		<item>
		<title>JavaScript and Other Client-Side Technologies</title>
		<link>http://readall.org/2008/03/16/javascript-and-other-client-side-technologies/</link>
		<comments>http://readall.org/2008/03/16/javascript-and-other-client-side-technologies/#comments</comments>
		<pubDate>Sun, 16 Mar 2008 09:17:27 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP]]></category>

		<category><![CDATA[Client-Side Technologies]]></category>

		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/16/javascript-and-other-client-side-technologies/</guid>
		<description><![CDATA[The various client-side technologies differ in many ways, starting with the way they get loaded and executed by the web client. JavaScript is a scripting language, whose code is written in plain text and can be embedded into HTML pages to empower them. When a client requests an HTML page, that HTML page can contain [...]]]></description>
			<content:encoded><![CDATA[<p>The various client-side technologies differ in many ways, starting with the way they get loaded and executed by the web client. JavaScript is a scripting language, whose code is written in plain text and can be embedded into HTML pages to empower them. When a client requests an HTML page, that HTML page can contain JavaScript. JavaScript is supported by all modern web browsers without requiring users to install new components on the system.<br />
JavaScript is a language in its own right (theoretically it isn&#8217;t tied to web development), it&#8217;s supported by most web clients under any platform, and it has some object-oriented capabilities. JavaScript is not a compiled language so it&#8217;s not suited for intensive calculations or writing device drivers and it must arrive in one piece at the client browser to be interpreted so it is not secure either, but it does a good job when used in web pages.<br />
 <a href="http://readall.org/2008/03/16/javascript-and-other-client-side-technologies/#more-25" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/16/javascript-and-other-client-side-technologies/feed/</wfw:commentRss>
		</item>
		<item>
		<title>PHP and Other Server-Side Technologies</title>
		<link>http://readall.org/2008/03/15/php-and-other-server-side-technologies/</link>
		<comments>http://readall.org/2008/03/15/php-and-other-server-side-technologies/#comments</comments>
		<pubDate>Sat, 15 Mar 2008 09:15:27 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP]]></category>

		<category><![CDATA[Server-Side Technologies]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/15/php-and-other-server-side-technologies/</guid>
		<description><![CDATA[Server-side web technologies enable the web server to do much more than simply returning the requested HTML files, such as performing complex calculations, doing object-oriented programming, working with databases, and much more.
Just imagine how much data processing Amazon must do to calculate personalized product recommendations for each visitor, or Google when it searches its enormous [...]]]></description>
			<content:encoded><![CDATA[<p>Server-side web technologies enable the web server to do much more than simply returning the requested HTML files, such as performing complex calculations, doing object-oriented programming, working with databases, and much more.<br />
Just imagine how much data processing Amazon must do to calculate personalized product recommendations for each visitor, or Google when it searches its enormous database to serve your request. Yes, server-side processing is the engine that caused the web revolution, and the reason for which Internet is so useful nowadays.<br />
 <a href="http://readall.org/2008/03/15/php-and-other-server-side-technologies/#more-24" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/15/php-and-other-server-side-technologies/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Redirecting to a Different Location</title>
		<link>http://readall.org/2008/03/14/redirecting-to-a-different-location/</link>
		<comments>http://readall.org/2008/03/14/redirecting-to-a-different-location/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 08:02:31 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP cookbook]]></category>

		<category><![CDATA[header]]></category>

		<category><![CDATA[location]]></category>

		<category><![CDATA[Redirecting]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/14/redirecting-to-a-different-location/</guid>
		<description><![CDATA[Problem
You want to automatically send a user to a new URL. For example,after successfully
saving form data, you want to redirect a user to a page that confirms the data.
Solution
Before any output is printed,use header() to send a Location header with the new
URL:
header('Location: http://www.example.com/');
Discussion
If you want to pass variables to the new page,you can include them [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Problem</strong><br />
You want to automatically send a user to a new URL. For example,after successfully<br />
saving form data, you want to redirect a user to a page that confirms the data.</p>
<p><strong>Solution</strong><br />
Before any output is printed,use header() to send a Location header with the new<br />
URL:<br />
<code>header('Location: http://www.example.com/');</code></p>
<p><strong>Discussion</strong><br />
If you want to pass variables to the new page,you can include them in the query<br />
string of the URL:<br />
<code>header('Location: http://www.example.com/?monkey=turtle');</code><br />
The URL that you are redirecting a user to is retrieved with GET. You can’t redirect<br />
someone to retrieve a URL via POST. You can,however,send other headers along<br />
with the Location header. This is especially useful with the Window-target header,<br />
which indicates a particular named frame or window in which to load the new URL:<br />
<code>header('Window-target: main');<br />
header('Location: http://www.example.com/');<br />
</code>The redirect URL must include the protocol and hostname; it can’t just be a pathname:<br />
<code>// Good Redirect<br />
header('Location: http://www.example.com/catalog/food/pemmican.php');<br />
// Bad Redirect<br />
header('Location: /catalog/food/pemmican.php');</code></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/14/redirecting-to-a-different-location/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Deleting Cookies</title>
		<link>http://readall.org/2008/03/13/deleting-cookies/</link>
		<comments>http://readall.org/2008/03/13/deleting-cookies/#comments</comments>
		<pubDate>Thu, 13 Mar 2008 08:49:48 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP cookbook]]></category>

		<category><![CDATA[deleting cookies]]></category>

		<category><![CDATA[setcookie]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/13/deleting-cookies/</guid>
		<description><![CDATA[Problem
You want to delete a cookie so a browser doesn’t send it back to the server.
Solution
Call setcookie() with no value for the cookie and an expiration time in the past:

setcookie('flavor','',time()-86400);
Discussion
It’s a good idea to make the expiration time a few hours or an entire day in the past,
in case your server and the user’s computer [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Problem</strong><br />
You want to delete a cookie so a browser doesn’t send it back to the server.</p>
<p><strong>Solution</strong><br />
Call setcookie() with no value for the cookie and an expiration time in the past:</p>
<pre CODE="name" CLASS="php">
setcookie('flavor','',time()-86400);</pre>
<p><strong>Discussion</strong><br />
It’s a good idea to make the expiration time a few hours or an entire day in the past,<br />
in case your server and the user’s computer have unsynchronized clocks. For example,<br />
if your server thinks it’s 3:06 P.M. and a user’s computer thinks it’s 3:02 P.M.,a<br />
cookie with an expiration time of 3:05 P.M. isn’t deleted by that user’s computer<br />
even though the time is in the past for the server.<br />
The call to setcookie() that deletes a cookie has to have the same arguments (except<br />
for value and time) that the call to setcookie() that set the cookie did,so include the<br />
path, domain, and secure flag if necessary.</p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/13/deleting-cookies/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Reading Cookie Values</title>
		<link>http://readall.org/2008/03/12/reading-cookie-values/</link>
		<comments>http://readall.org/2008/03/12/reading-cookie-values/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 08:00:17 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP cookbook]]></category>

		<category><![CDATA[$_COOKIE]]></category>

		<category><![CDATA[cookie]]></category>

		<category><![CDATA[Reading]]></category>

		<category><![CDATA[Values]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/12/reading-cookie-values/</guid>
		<description><![CDATA[Problem
You want to read the value of a cookie that’s been previously set.
Solution
Look in the $_COOKIE superglobal array:

if (isset($_COOKIE['flavor'])) {
print "You ate a $_COOKIE[flavor] cookie.";
}
Discussion
A cookie’s value isn’t available in $_COOKIE during the request in which the cookie is
set. In other words,the setcookie() function doesn’t alter the value of $_COOKIE. On
subsequent requests,however,each cookie is stored [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Problem</strong><br />
You want to read the value of a cookie that’s been previously set.<br />
Solution<br />
Look in the $_COOKIE superglobal array:</p>
<pre NAME="code" CLASS="php">
if (isset($_COOKIE['flavor'])) {
print "You ate a $_COOKIE[flavor] cookie.";
}</pre>
<p><strong>Discussion</strong><br />
A cookie’s value isn’t available in $_COOKIE during the request in which the cookie is<br />
set. In other words,the setcookie() function doesn’t alter the value of $_COOKIE. On<br />
subsequent requests,however,each cookie is stored in $_COOKIE. If register_globals<br />
is on, cookie values are also assigned to global variables.<br />
When a browser sends a cookie back to the server,it sends only the value. You can’t<br />
access the cookie’s domain,path,expiration time,or secure status through $_COOKIE<br />
because the browser doesn’t send that to the server.<br />
To print the names and values of all cookies sent in a particular request,loop<br />
through the $_COOKIE array:</p>
<pre NAME="code" CLASS="php">
foreach ($_COOKIE as $cookie_name =&gt; $cookie_value) {
print "$cookie_name = $cookie_value&lt;br&gt;";
}</pre>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/12/reading-cookie-values/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Setting Cookies</title>
		<link>http://readall.org/2008/03/11/setting-cookies/</link>
		<comments>http://readall.org/2008/03/11/setting-cookies/#comments</comments>
		<pubDate>Tue, 11 Mar 2008 07:55:11 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP cookbook]]></category>

		<category><![CDATA[cookie]]></category>

		<category><![CDATA[Cookies]]></category>

		<category><![CDATA[setcookie]]></category>

		<category><![CDATA[Setting]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/26/setting-cookies/</guid>
		<description><![CDATA[Problem
You want to set a cookie.
Solution
Use setcookie():

setcookie('flavor','chocolate chip');
Discussion
Cookies are sent with the HTTP headers,so setcookie() must be called before any
output is generated. You can pass additional arguments to setcookie() to control cookie behavior. The
third argument to setcookie() is an expiration time,expressed as an epoch timestamp.
]]></description>
			<content:encoded><![CDATA[<p><strong>Problem</strong><br />
You want to set a cookie.<br />
Solution<br />
Use setcookie():</p>
<pre NAME="code" CLASS="php">
setcookie('flavor','chocolate chip');</pre>
<p><strong>Discussion</strong><br />
Cookies are sent with the HTTP headers,so setcookie() must be called before any<br />
output is generated. You can pass additional arguments to setcookie() to control cookie behavior. The<br />
third argument to setcookie() is an expiration time,expressed as an epoch timestamp.<br />
 <a href="http://readall.org/2008/03/11/setting-cookies/#more-18" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/11/setting-cookies/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Program: Abusive User Checker</title>
		<link>http://readall.org/2008/03/10/program-abusive-user-checker/</link>
		<comments>http://readall.org/2008/03/10/program-abusive-user-checker/#comments</comments>
		<pubDate>Mon, 10 Mar 2008 09:50:45 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[PHP cookbook]]></category>

		<category><![CDATA[Abusive]]></category>

		<category><![CDATA[Checker]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/21/program-abusive-user-checker/</guid>
		<description><![CDATA[Shared memory’s speed makes it an ideal way to store data different web server processes need to access frequently when a file or database would be too slow. Example  shows the pc_Web_Abuse_Check class,which uses shared memory to track accesses to web pages in order to cut off users that abuse a site by bombarding [...]]]></description>
			<content:encoded><![CDATA[<p>Shared memory’s speed makes it an ideal way to store data different web server processes need to access frequently when a file or database would be too slow. Example  shows the pc_Web_Abuse_Check class,which uses shared memory to track accesses to web pages in order to cut off users that abuse a site by bombarding it with requests.</p>
<p> <a href="http://readall.org/2008/03/10/program-abusive-user-checker/#more-17" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/10/program-abusive-user-checker/feed/</wfw:commentRss>
		</item>
		<item>
		<title>JavaScript Application Cookbook</title>
		<link>http://readall.org/2008/03/09/javascript-application-cookbook/</link>
		<comments>http://readall.org/2008/03/09/javascript-application-cookbook/#comments</comments>
		<pubDate>Sun, 09 Mar 2008 09:18:03 +0000</pubDate>
		<dc:creator>LANC</dc:creator>
		
		<category><![CDATA[JavaScript]]></category>

		<category><![CDATA[Application]]></category>

		<category><![CDATA[Cookbook]]></category>

		<guid isPermaLink="false">http://readall.org/2008/03/17/javascript-application-cookbook/</guid>
		<description><![CDATA[
There is a serious information gap for Webmasters learning client-side JavaScript skills and trying to solve common Web-related problems. Knowing the syntax is one thing, being able to build a useful application is another. And while there are dozens of &#8220;how- to&#8221; JavaScript books available, few literally hand the Webmaster a set of ready-to-go, client-side [...]]]></description>
			<content:encoded><![CDATA[<p STYLE="text-align: center"><img HEIGHT="236" WIDTH="180" BORDER="0" SRC="http://www.oreilly.com/catalog/covers/1565925777_cat.gif" /></p>
<p>There is a serious information gap for Webmasters learning client-side JavaScript skills and trying to solve common Web-related problems. Knowing the syntax is one thing, being able to build a useful application is another. And while there are dozens of &#8220;how- to&#8221; JavaScript books available, few literally hand the Webmaster a set of ready-to-go, client-side JavaScript applications with thorough documentation that enable the reader to fully understand and extend those applications. By providing such a set of applications, JavaScript Application Cookbook allows Webmasters to immediately add extra functionality to their Web sites. This book targets readers with two different skill sets. The primary target is JavaScript-knowledgeable Webmasters and designers who can immediately begin constructing their own versions of the applications. The secondary target is those with little or no JavaScript experience. The included applications are ready for immediate use and require little customization. This book explores both the code and the techniques that are centered around core JavaScript functionality, a functionality that will not become incompatible or obsolete. The source file design of most applications and libraries will help modularize reader Web sites and facilitate easier site management and coding practices. Chapters are organized by application. Among the included applications are:<br />
A client-side search engine that will show coders how to build their own search engine and get excellent results, all with a client-side tool<br />
A drag-and-drop greeting application that lets users custom build and send DHTML email greetings<br />
A GUI image rollover tool that generates cross-browser image rollover code for all versions of JavaScript<br />
A robust client-side shopping cart application that lets shoppers browse and shop, while the application keeps a tab of the shopper&#8217;s selections and a running bill, including tax and shipping<br />
An online test application that auto-administers, grades, and displays answers to online exams or surveys<br />
An additional value to this book is an online resource (http://www.serve.com/hotsyte/) that discusses the applications and points to other resources. With its focus on providing practical real-world solutions for Webmasters, JavaScript Application Cookbook is destined to become a staple for every JavaScript developer, regardless of experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://readall.org/2008/03/09/javascript-application-cookbook/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
