com.db4o

Interface ObjectServer

All Known Subinterfaces:

ExtObjectServer

public interface ObjectServer

the db4o server interface.

- db4o servers can be opened with Db4o.openServer(String, int).
- Direct in-memory connections to servers can be made with openClient()
- TCP connections are available through Db4o.openClient(String, int, String, String).

Before connecting clients over TCP, you have to grantAccess(String, String) to the username and password combination that you want to use.

See Also:

Db4o.openServer, ExtObjectServer for extended functionality

Method Summary

Methods

Modifier and Type	Method and Description
boolean	close() closes the ObjectServer and writes all cached data.
ExtObjectServer	ext() returns an ObjectServer with extended functionality.
void	grantAccess(java.lang.String userName, java.lang.String password) grants client access to the specified user with the specified password.
ObjectContainer	openClient() opens a client against this server.

Method Detail

close

boolean close()

closes the ObjectServer and writes all cached data.

Returns:

true - denotes that the last instance connected to the used database file was closed.

ext

ExtObjectServer ext()

returns an ObjectServer with extended functionality.

Use this method as a convenient accessor to extended methods. Every ObjectServer can be casted to an ExtObjectServer.

The functionality is split to two interfaces to allow newcomers to focus on the essential methods.

grantAccess

void grantAccess(java.lang.String userName,
               java.lang.String password)

grants client access to the specified user with the specified password.

If the user already exists, the password is changed to the specified password.

Parameters:

userName - the name of the user

password - the password to be used

openClient

ObjectContainer openClient()

opens a client against this server.

A client opened with this method operates within the same VM as the server. Since an embedded client can use direct communication, without an in-between socket connection, performance will be better than a client opened with Db4o.openClient(java.lang.String, int, java.lang.String, java.lang.String)

Every client has it's own transaction and uses it's own cache for it's own version of all peristent objects.