op=rdf with large number of mp3 files (12,000)

Trying to grab an RDF listing from mod_mp3, with about 12,000 songs in
the collection. After 2m11.391s, the client process simply stops. Apache
server Timeout is set to 0. The rdf file looks like this (hostname
changed to protect the innocent):

<?xml version="1.0" encoding="ISO-8859-1"?>
 
<rdf:RDF
                xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
                xmlns="http://purl.org/rss/1.0/"
                xmlns:audio="http://media.tangent.org/rss/1.0/"
                xmlns:dc="http://purl.org/dc/elements/1.1/"
                xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
        >
        <channel rdf:about="http://hostmame8000:/">
                <title>Apache/mod_mp3 cast</title>
                <description>misc</description>
                <pubDate>Tue Jul 30 20:26:44 2002</pubDate>
                <lastBuildDate>Tue Jul 30 20:26:44 2002</lastBuildDate>
                <webMaster>webmaster@hostname</webMaster>
                <link>http://hostname:8000/</link>
 
                <items>
                        <rdf:Seq>
                                <rdf:li
rdf:resource="http://hostname:8000/?op=play&amp;song=00067cdc0e28e99683308843b2c34f58" />
....
 <rdf:li
rdf:resource="http://hostname:8000/?op=play&amp;song=fffb32949dfc00f9d3cf525c169b5163" />
                        </rdf:Seq>
                </items>
        </channel>

I ran top on the server, and noticed the process seemed to grow to about
577Mb, then stop.

My question is: Is this something that someone else has gotten to work?
Has rdf been abandoned?

A peek at the source code suggests that each track should be sent off
instantly as soon as it's done, but 'top' suggests that it's trying to
assemble the entire document before shipping it off.

If anyone has any suggestions, or if I can provide more useful
information, please let me know.

Thanks,

Rob