iPEP® Technology
iPEP® Procedures
Identification:
- Session cookie assigns unique client ID to browser cookie pool.
- All HTTP connections (get requests) to iPEP controlled URLs can then be identified as belonging to this client.
Prioritisation:
- iPEP maintains content policies that can define a client’s Priority based on the Target and/or Referring URL string in the HTTP headers. A default Priority is assigned if no content policy is met.
- Web servers or other external programming can override the Priority assigned by iPEP using various APIs. For example, if there is a login to the website Priority can be governed by who the user is.
Activation:
- iPEP maintains an activation policy per definable priority (Priority Class) and one to cover all connections. Activation policies determine how many concurrent connections per client and concurrent client connections can be actively communicating to the WebServer.
- iPEP monitors accessibility, demand and server response times for each Priority Class automatically whilst always maintaining the ability for all levels of Priority Class to have some access.
- During periods where demand exceeds all capacity to reasonably provision the requests for each Priority Class, iPEP will automatically queue the client connections. At definable intervals the position on the queue along with other applicable messages/adverts is presented back to the client browser, so they are aware that queuing is taking place and where they are in the queue.
- When the maximum queue size is reached the client connections are re-directed to an “Overload” URL or sent definable HTML directly to the browser.
- Once a client becomes “Active” all their connections will be served and the client will remain active for a definable number of seconds. If there are no new connections in this time period, they will be subject to all the activation tests again.
[ back to top ]