Master Server Session Manager

From RemObjects Software

This is a RemObjects SDK Architecture entry
Feel free to add your notes to this topic below.

This session manager will use the precompiled Master Server back-end database to store data in a data table and use RemObjects SDK itself to communicate with the Master Server.

Basically, the Master Server is a standalone database server (based on the powerful NexusDB 2.0 database engine) that you can run on one host in your server farm to store session data. You can then use use the Master Server Session Manager component in your RemObjects SDK server(s) and access this common server to store and locate session data.

Use Cases

Use these session managers when you need session data to persist between server restarts, or during crashes and power outages, or if you are deploying several server executables - either on the same hardware or across a server farm - that need to share the same session data.

You will use Master Server instead of the other database-driven session managers if you do not want to setup or maintain a full database or database server for session data.

Components

• MasterServerSessionManager (.NET)
• TROMasterServerSessionManager (Delphi)

See Also

• Master Server
• Session Management
  • Database Session Manager
  • Event-Driven Session Manager
  • In-Memory Session Manager
• Statelessness
• Class Factories
• Lists
  • Namespaces
  • Classes: .NET — Delphi
  • Interfaces: .NET — Delphi
  • Enums: .NET — Delphi
  • Types: Data — File

Product: RemObjects SDK
Current version: RemObjects SDK 'Vinci' (5.0)

Lists — Glossary — Features — How To — Components — Tools — Samples — Articles — Architecture — Issues