This shows you the differences between two versions of the page.
Next revision Both sides next revision | |||
admin:basics:network:home [2011/04/13 13:05] doc created |
admin:basics:network:home [2011/04/13 15:04] doc |
||
---|---|---|---|
Line 16: | Line 16: | ||
==== Overview ==== | ==== Overview ==== | ||
+ | |||
+ | Omnidex Network Services provide the core communication interface between the components of Omnidex. Based upon the TCP/IP standard, Omnidex Network Services provides the communication services for Omnidex's [[integration:odbc:home|ODBC]] and [[integration:jdbc:home|JDBC]] drivers, as well as the internal communication used in [[admin:features:grids:home|Omnidex Grids]]. | ||
+ | |||
+ | Omnidex Network Services normally runs as a service in Microsoft Windows, or as a background daemon on Linux. The main process, called OdxNet, will listen for network requests and spawn additional processes to service each request. It is common to see many OdxNet processes running on an Omnidex server, each one handling a request from a user. Note that OdxNet favors a separate process for each request to help improve control and stability of the application. | ||
+ | |||
+ | Omnidex Network Services provide additional services to provide security and pooling to Omnidex applications. Communication through Omnidex Network Services is automatically encrypted and compressed to preserve security. Connection pooling can also be configured to improve overall performance of Omnidex applications. | ||
+ | |||
+ | Omnidex Network Services provide the core communication link for Omnidex Grids. To insure the best performance of Omnidex Grids, Omnidex Network Services is generally configured for each grid to create pools for the grid nodes. | ||