svn commit: r848406 - in /websites/staging/jena/trunk/content: ./ documentation/io/index.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jan 29 10:39:49 2013
New Revision: 848406

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/io/index.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan 29 10:39:49 2013
@@ -1 +1 @@
-1439198
+1439822

Modified: websites/staging/jena/trunk/content/documentation/io/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/io/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/io/index.html Tue Jan 29 10:39:49 2013
@@ -433,13 +433,13 @@ configuration file is necessary.</p>
 <p>One of the capabilities of the RIOT API is the ability to treat parser output as an iterator, 
 this is useful when you don't want to go to the trouble of writing a full sink implementation and can easily express your
 logic in normal iterator style.</p>
-<p>To do this you use one of the subclasses of <a href="http://svn.apache.org/viewvc/jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/lang/StreamedRDFIterator.java?view=markup">StreamedRDFIterator</a>
-which is an abstract class that implements the <a href="http://svn.apache.org/viewvc/jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/lang/RDFParserOutputIterator.java?view=markup">RDFParserOutputIterator</a> interface.
-This interface provides an implementation of StreamRDF which allows it to consume parser output and an implementation
-of a standard Java iterator allowing it to provide output in the normal iterator paradigm.  This has some advantages
-over a direct StreamRDF implementation since it allows the parser production of data to run
-ahead of your consumption of data which may result in better overall throughput.</p>
-<p>The only complication is that you need to ensure that the parser and the consumer of the iterator are on different threads
+<p>To do this you use one of the subclasses of 
+<a href="http://svn.apache.org/viewvc/jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/lang/PipedRDFIterator.java?view=markup">PipedRDFIterator</a>
+in conjunction with a <a href="http://svn.apache.org/viewvc/jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/lang/PipedRDFStream.java?view=markup">PipedRDFStream</a>.</p>
+<p>This <code>PipedRDFStream</code> provides an implementation of <code>StreamRDF</code> which allows it to consume parser output and this is consumed by
+the <code>PipedRDFIterator</code> implementation.  This has some advantages over a direct <code>StreamRDF</code> implementation since it allows the parser 
+production of data to run ahead of your consumption of data which may result in better overall throughput.</p>
+<p>The only complication is that you need to ensure that the thread feeding the <code>PipedRDFStream</code> and the consumer of the iterator are on different threads
 as otherwise you can run into a deadlock situation where one is waiting on data from the other which is never started.</p>
 <p>See <a href="https://svn.apache.org/repos/asf/jena/trunk/jena-arq/src-examples/arq/examples/riot/ExRIOT_6.java">RIOT example 6</a> 
 which shows an example usage including a simple way to push the parser onto a different thread to avoid the possible deadlock.</p>