Soprano::Client Namespace Reference

The Client module provides classes to connect to remote RDF sources, most important the Soprano Server which can be connected via DBus, a local socket, or TCP (see below). More...

Classes
class	DBusClient
	Core class to handle a connection to a Soprano server through the DBus interface. More...
class	DBusModel
	Interface to a DBus server model. More...
class	DBusNodeIterator
	Interface to a DBus server node iterator. More...
class	DBusQueryResultIterator
	Interface to a DBus server query result iterator. More...
class	DBusStatementIterator
	Interface to a DBus server statement iterator. More...

---

Detailed Description

The Client module provides classes to connect to remote RDF sources, most important the Soprano Server which can be connected via DBus, a local socket, or TCP (see below).

Apart from the Soprano Server, arbitrary SPARQL Http services can be connected via SparqlModel.

Overview of the Soprano Server clients

The Soprano Server clients have the following restrictions:

TCP Client: (TcpClient)

• No signals are emitted (Model::statementsAdded() and Model::statementsRemoved())
• No permission handling, i.e. each process running on the machine can access a running Soprano server, indifferent of the user id of the server process.

Local Socket Client: (LocalSocketClient)

• No signals are emitted (Model::statementsAdded() and Model::statementsRemoved())

DBus Client: (DBusClient)

• No restrictions

While the local socket comunication is the fastest due to its missing signal handling it can be sub-optimal at times. The best solution at the moment is the DBus client. Although being the slowest (slightly slower than the local Socket client) it is reliable and feature-complete (signals are transmitted). However, it is also possible to combine both: use the local socket communication for fast commands and create a D-Bus connection only for the signals.

See also:

Soprano::Server, Soprano D-Bus Interface