Site Menu
- Home
- Products
- NexusDB
- Nexus Quality Suite
- NexusDB Drivers & Connectors
- Nexus Remoting
- Nexus Memory Manager
- Some of our Customers
- Testimonials and use(r)s
- Downloads
- Documentation
- Support
- Pricing & Orders
- About
- Community
- My Nexus
- Recently Updated ...
- Search...
- Site Login
Search
How does "Automatic Physical Connection sharing" work and what are its benefits?
Without going into too much detail, the transports internally use a pool of physical connections (sockets, named pipes, shared memory sections) there is no 1:1 relationship between physical connections and opened sessions. Your client application can have 500 threads, each has opened 5 sessions, all using the same transport. If only 10 threads of these are actually inside a call to the server at the same time only 10 physical connections will be required for 2500 sessions. Opening a new session just requires a message over an already existing physical connection, instead of establishing a new connection.
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