<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Information Design&gt;Databases</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Databases</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Information Design and Databases in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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>Design&gt;Web Design&gt;Information Design&gt;Databases</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Databases</link>
	</image>
	<item>
		<title>Consistency-Preserving Caching of Dynamic Database Content</title>
		<link>http://tc.eserver.org/34194.html</link>
		<guid>http://tc.eserver.org/34194.html</guid>
		<description>With the growing use of dynamic web content generated from relational databases, traditional caching solutions for throughput and latency improvements are ineffective. We describe a middleware layer called Ganesh that reduces the volume of data transmitted without semantic interpretation of queries or results. It achieves this reduction through the use of cryptographic hashing to detect similarities with previous results. These beneﬁts do not require any compromise of the strict consistency semantics provided by the back-end database. Further, Ganesh does not require modiﬁcations to applications, web servers, or database servers, and works with closed-source applications and databases. Using two benchmarks representative of dynamic web sites, measurements of our prototype show that it can increase end-to-end throughput by as much as twofold for non-data intensive applications and by as much as tenfold for data intensive ones.</description>
	</item>
	<item>
		<title>Storing Hierarchical Data in a Database</title>
		<link>http://tc.eserver.org/22406.html</link>
		<guid>http://tc.eserver.org/22406.html</guid>
		<description>Whether you want to build your own forum, publish the messages from a mailing list on your Website, or write your own CMS: there will be a moment that you&apos;ll want to store hierarchical data in a database. And, unless you&apos;re using a XML-like database, tables aren&apos;t hierarchical; they&apos;re just a flat list. You&apos;ll have to find a way to translate the hierarchy in a flat file.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Databases.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>