incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-203) support for Non Blocking Parsers
Date Fri, 02 Mar 2012 15:29:57 GMT


Andy Seaborne commented on JENA-203:

I can image it has no impact on existing Jena API.  I think is the wrong way
round and it should  The FileManager has that design ; I'm imaging
"ReadEngine.many(model, set of places, waitForAll?)" would be the way to get from 500 places
at once.

The new WebReader I have ready to go also does that where there is only one RDF reader for
all syntaxes and routes to that.  The syntax is merely a hint, and only one or
several pieces of information used to determine the specific parser.

If your parser does encounter a large, fast reply stream - how fast does it parse?

> support for Non Blocking Parsers
> --------------------------------
>                 Key: JENA-203
>                 URL:
>             Project: Apache Jena
>          Issue Type: Improvement
>            Reporter: Henry Story
> In a Linked Data environment servers have to fetch data off the web. The speed at which
such data 
> is served can be very slow. So one wants to avoid using up one thread for each connections
(1 thread = 
> 0.5 to 1MB approximately). This is why Java NIO was developed and why servers such as
> are so popular, why http client libraries such as
are more
> and more numerous, and why framewks such as which support relatively
> actors (500 bytes per actor) are growing more viisible.
> Unless I am mistaken the only way to parse some content is using methods that use an

> InputStream such as this:
>     val m = ModelFactory.createDefaultModel()
>      m.getReader(lang.jenaLang).read(m, in, base.toString)
> That read call blocks. Would it be possible to have an API which allows
> one to parse a document in chunks as they arrive from the input?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message