For documentation on the current version, please check Knowledge Base.
Session Control
This section explains how sessions are requested and how you can choose to take control over the creation of sessions.
About Sessions
Orbit FlashMap is designed to work with sessions, every session (by default) expires in exactly 15 minutes.
When the FlashMap client starts it requires a session identifier from the server.
Without a valid session the server will just ignore requests from the client.
At startup FlashMap looks for a SessionID in the following places :
- In the FlashVars arguments
- By dynamically requesting a session from the server.
Securing Sessions
The second option (requesting a session from the server) can be secured by moving the CreateSession operation to another service, which may be operating on another portnumber that's not accessible to the internet. The web application can then request sessions at the administrative service, and provide them to FlashMap as a FlashVars argument.
The result is a setup where only yoúr web application can supply sessions, thus securing your website from unauthorized access by third parties.
Why would we do that ?
Some webmasters want to avoid the misuse of their website. This technique allows you to secure your website from access that is not explicitly granted by your web application.