<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Restrict Access based on User Level on a per-post basis</title>
	<atom:link href="http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/</link>
	<description></description>
	<lastBuildDate>Tue, 10 Jan 2012 01:21:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: skippy</title>
		<link>http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/comment-page-1/#comment-12811</link>
		<dc:creator>skippy</dc:creator>
		<pubDate>Thu, 07 Oct 2004 17:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/#comment-12811</guid>
		<description>As the author of the mod, I&#039;d like to point out the fundamental difference between the plugin and my mod.

The plugin filters posts to display &lt;strong&gt;after&lt;/strong&gt; they&#039;ve been pulled from the database, whereas my mod changes the SQL query to prevent restricted posts from even being returned by the database.  I&#039;ve always been told to pull from the database &lt;em&gt;only&lt;/em&gt; what you&#039;re going to use, so I wrote my mod to make sure that only the posts that the reader ought to see are ever pulled.

The difference is subtle, and probably even negligent for most people.  But for a very busy site, or a site with a lot of restricted posts, (and possibly for a site running on less powerful hardware) my mod should provide better long-term performance.</description>
		<content:encoded><![CDATA[<p>As the author of the mod, I&#039;d like to point out the fundamental difference between the plugin and my mod.</p>
<p>The plugin filters posts to display <strong>after</strong> they&#039;ve been pulled from the database, whereas my mod changes the SQL query to prevent restricted posts from even being returned by the database.  I&#039;ve always been told to pull from the database <em>only</em> what you&#039;re going to use, so I wrote my mod to make sure that only the posts that the reader ought to see are ever pulled.</p>
<p>The difference is subtle, and probably even negligent for most people.  But for a very busy site, or a site with a lot of restricted posts, (and possibly for a site running on less powerful hardware) my mod should provide better long-term performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carla</title>
		<link>http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/comment-page-1/#comment-12808</link>
		<dc:creator>Carla</dc:creator>
		<pubDate>Thu, 07 Oct 2004 16:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.scriptygoddess.com/archives/2004/10/07/restrict-access-based-on-user-level-on-a-per-post-basis/#comment-12808</guid>
		<description>I use Skippy&#039;s user level hack on one of my blogs and I am REALLY happy with it. I tried the plugin but I couldn&#039;t get it to work. :( The user level hack is amazing. Why MT doesn&#039;t have something like it, I don&#039;t know....</description>
		<content:encoded><![CDATA[<p>I use Skippy&#039;s user level hack on one of my blogs and I am REALLY happy with it. I tried the plugin but I couldn&#039;t get it to work. <img src='http://www.scriptygoddess.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  The user level hack is amazing. Why MT doesn&#039;t have something like it, I don&#039;t know&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

