<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.network.sn">
    <title>gmane.network.sn</title>
    <link>http://permalink.gmane.org/gmane.network.sn</link>
    <description></description>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq><rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.sn/1048"/>
 </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.sn/1048">
    <title>Bypass XHDR</title>
    <link>http://permalink.gmane.org/gmane.network.sn/1048</link>
    <description>&lt;pre&gt;First, it needs to be stated emphatically that I am not a C programmer! 
All I can do is copy code and then hack it until it does what I want, or
I admit defeat and give up.

The reason for this patch is that I wanted to suck a newsgroup with over
5 million articles; it was taking about 7 hours to run XHDR.  In my
opinion, XHDR is a complete waste of time for a news server because it
downloads the entire article and never just the headers.  In addition to
the wasted 7 hours, my upstream NNTP server - newsguy - places a
limitation on either the number of articles or the number of bytes
downloaded in a single setting, and sends "503 transfer limit, closing
connection." when that limit is reached.  I didn't time it, but my guess
is that the actual article download ran for 10 or 11 hours before the
503 error.  Thus, each attempt consumed 17 or 18 hours, of which
something like 40% was totally wasted.  Worse, if I allowed snfetch to
automatically restart, it would begin with the original .serial number
value and &lt;/pre&gt;</description>
    <dc:creator>gypsy</dc:creator>
    <dc:date>2012-02-09T23:43:28</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.sn">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.sn</link>
  </textinput>
</rdf:RDF>
