<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Slaughter, Harry</title>	<link>http://tc.eserver.org/authors/Slaughter,_Harry</link>
	<description>A bibliography of works by Slaughter, Harry in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Slaughter, Harry</title>
		<link>http://tc.eserver.org/dir/Slaughter,_Harry</link>
	</image>
	<item>
		<title>Opcode Cache for Dummies</title>
		<link>http://tc.eserver.org/33880.html</link>
		<guid>http://tc.eserver.org/33880.html</guid>
		<description>PHP is an interpreted language. This means that each time a PHP generated page is requested, the server must read in the various files needed and &quot;compile&quot; them into something the machine can understand (opcode). A typical Drupal page requires more than a dozen of these bits of code be compiled. Opcode cache mechanisms preserve this generated code in cache so that it need only be generated a single time to server hundreds or millions of subsequent requests. Enabling opcode cache will reduce the time it takes to generate a page by up to 90%.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Slaughter,_Harry.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>