Components on the VCL Palette
Wed, 03/04/2009 - 20:02 | 
hdanzl
When the NexusDB design time package is installed into the IDE the palette contains a tab that will look like this (contents abbreviated; Delphi 2005 and newer).
Here's a short description of what each component is and what its place is in NexusDB. All components and their key properties are described in the following sub sections. If you're looking for a full reference please see the Source Reference book.
The NexusDB session component. Required component to connect your database/table/query components to a remote or embedded server engine component.
The NexusDB equivalent of TDatabase. Provides alias and database path handling. Not required, although for manageability reasons it's recommended to use one.
The NexusDB equivalent of TTable. Used for navigational access to tables by a NexusDB server.
The NexusDB TQuery equivalent. Extensive support for ANSI SQL/DDL provides strong access and data manipulating capabilities.
The backup controller allows backups with full data integrity at any time, even if the server is running 24/7.
The server engine contains the core NexusDB engine. Drop one on a form or data module in your application to create a single user database application. Connect with transports, SQLEngine etc to create custom stand-alone database servers.
Client-side server engine. Together with a transport, it provides remote access to data on a stand-alone server.
SQL engine Required for single-user applications that use SQL statements (TnxQuery components), or in standalone servers.
Used to develop server-side modules that monitors events (table open, record update, etc) and performs actions based on those events. Use to extend the server functionality.
The server command handler is responsible for decoding client requests, translation and forwarding of this request to the server engine and issuing the results back to the client.
This component connects two machines via TCP/IP (Winsock). At least one of the transports is required to create a client application that connects to a remote server.
This component connects two machines via Named Pipes. At least one of the transports is required to create a client application that connects to a remote server.
TnxBlowfishRC4SecuredTransport
This is a wrapper transport that can be used to make other transports (TCP, Named Pipes etc) secure.
Commandhandler used with the Secured transport above.
Command handler that does not depend on any database components. Use if you need to create a message system or similar that doesn't require database functionality.
Session component that does not depend on any database components. Use if you need to create a message system or similar that doesn't require database functionality.
Server-side plug-in example component that implements a few nice to have utility functions (get server-side time, get unique server ID).
The client-side plug-in example component for accessing the TnxServerInfoPlugin functions from a remote client.
TnxServerInfoPluginCommandHandler
Use this on the server side to route messages from remote clients to the TnxServerInfoPlugin.
server plugin for client access rights
This component manages a server engine (and all its attached server modules) and their settings.
filter that exposes events to limit client access to the server to clients with specific IP addresses
component to map different database/servers to one logical database
threaded session pool
to have multiple databases take part in the same transaction, connect them to the same transaction context
component to access SQL stored procedures
dataset that is loaded from an existing table (typically, client-side caching of server data)
component to write changes to the cached dataset back to the server
in-memory table
required to make the sql engine use triggers
transport for use when client and server are on the same machine
component that saves log entries to disk
The event log is a centralized way for handling log entries. All the other components can be connected to a single event log.
uses events to fetch data for logging
logs entries to the windows system log
links in all engines necessary to open version 1 tables
links in all engines necessary to open version 2 tables
Tags:
Questions? Problems?
- Interested to buy but something put you off?
- Can't find what you're looking for?
- Have a suggestion?
Let us know. If you're having trouble contacting us, please check here.
Site Updates
- Dec 4 2024 - 1:53pm
- Dec 4 2024 - 1:48pm
- Nov 19 2024 - 1:04pm
- Oct 17 2024 - 10:27am
- Jul 24 2024 - 1:22pm