Uses of Package
org.eclipse.emf.cdo.server

Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the IStoreAccessor API.

A simple HTTP server that web browsers can connect to in order to render internal server data for debugging purposes.

A server browser for the repositories in a managed container.

A server browser page that renders revisions.

Binary constants being used by both exporters and importers.

XML constants being used by both exporters and importers.

Persists the data that has been read by a importer into a new repository.

A call-back interface primarily intended to allow implementers to prevent the view from being opened by throwing an exception.

A query language handler that is capable of executing a query.

A CDO repository.

Provides a way to handle revisions that are to be sent to the client.

The server-side representation of a client session.

Represents the physical data storage back-end of a CDO repository, such as a database or a file system folder.

Enumerates the possible data formats a store can accept for commit operations.

Enumerates the possible history recording options a store can accept.

Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the IStoreAccessor API.

An extension interface for store accessors that support durable locking.

Represents the query execution state of a XRefs query.

Reads chunks of partially loaded lists from a physical data storage backend.

A repository with the ability to synchronize its content with another repository.

The server-side representation of a client view.

A CDO repository.

Provides the consumer with query handlers that are capable of executing queries represented by specific query infos.

Represents the physical data storage back-end of a CDO repository, such as a database or a file system folder.

Represents a connection to a physical data storage back-end.

An extension interface for store accessors that support raw data access as needed by repository synchronizers or server importers.

Reads chunks of partially loaded lists from a physical data storage backend.

Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the IStoreAccessor API.

Represents the query execution state of a XRefs query.

A CDO repository.

Provides the consumer with query handlers that are capable of executing queries represented by specific query infos.

Represents the physical data storage back-end of a CDO repository, such as a database or a file system folder.

Represents a connection to a physical data storage back-end.

An extension interface for store accessors that support durable locking.

The server-side representation of a client transaction.

Represents the physical data storage back-end of a CDO repository, such as a database or a file system folder.

Provides the consumer with query handlers that are capable of executing queries represented by specific query infos.

Represents a connection to a physical data storage back-end.

Provides the consumer with CDO repositories specified by their name.

A repository with the ability to synchronize its content with another repository.

Represents the execution state of a query in the server towards a query handler.

Represents a connection to a physical data storage back-end.

A CDO repository.

A CDO repository.

Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the IStoreAccessor API.

Manages all persistent aspects of durable CDO views and provides for vetoable interception of the durable view resumption process.

A query language handler that is capable of executing a query.

A CDO repository.

Provides a way to handle commits that are received from a client.

Protects a repository by authenticating users and, optionally, authorizing read and write operations.

Synchronizes a synchronizable repository with a master repository.

Manages the user sessions of a repository.

Enumerates the possible data formats a store can accept for commit operations.

Enumerates the possible history recording options a store can accept.

Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the IStoreAccessor API.

Represents the query execution state of a resources query that is supposed to deliver one exact resource, or null.

Represents a sublist of consecutive elements that are subject to partial collection loading.

A repository with the ability to synchronize its content with another repository.

An extension interface for store accessors that support raw data access as needed by repository synchronizers or server importers.

Represents the physical data storage back-end of a CDO repository, such as a database or a file system folder.