You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "A. Soroka (JIRA)" <ji...@apache.org> on 2017/03/12 18:51:04 UTC

[jira] [Closed] (JENA-226) New Client API

     [ https://issues.apache.org/jira/browse/JENA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A. Soroka closed JENA-226.
--------------------------
    Resolution: Implemented

See comment by [~andy.seaborne].

> New Client API
> --------------
>
>                 Key: JENA-226
>                 URL: https://issues.apache.org/jira/browse/JENA-226
>             Project: Apache Jena
>          Issue Type: New Feature
>            Reporter: Stephen Allen
>            Assignee: Stephen Allen
>            Priority: Minor
>
> Develop a new API geared towards bridging the gap between local Jena databases and remote SPARQL HTTP endpoints.  This would provide a single object to represent a repository, and provide functions to perform querying and modification of the data in the repository.  These functions would attempt to be as efficient as possible (i.e. streaming modifications to remote servers), while also promoting safe practices such as parameterizing user supplied query inputs to prevent SPARQL-injection attacks.
> I've started writing up some use cases at [1] (would like to move over to the Confluence Wiki shortly).  And I've also started a branch [2] (not much there yet).  Feedback is greatly appreciated.
> [1] http://people.apache.org/~sallen/jena/ClientUseCases.html
> [2] http://svn.apache.org/repos/asf/incubator/jena/Jena2/ARQ/branches/ArqClient



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)