Update README.md

simplified readme with link to server-side documentation repo

Author: frwiqueueit

README.md

@@ -1,50 +1,9 @@
->You can find the latest released version [here](https://github.com/queueit/KnownUser.V3.Python/releases/latest)
-
 # KnownUser.V3.Python
-The Queue-it Security Framework is used to ensure that end users cannot bypass the queue by adding a server-side integration to your server. It was developed and verified with Python v.2.7 and Django v.1.8. Please reach out to us if you are using another web framework, so we add it to the supported providers.
-
-## Introduction
-When a user is redirected back from the queue to your website, the queue engine can attache a query string parameter (`queueittoken`) containing some information about the user. 
-The most important fields of the `queueittoken` are:
-
- - q - the users unique queue identifier
- - ts - a timestamp of how long this redirect is valid
- - h - a hash of the token
-
-
-The high level logic is as follows:
-
-![The KnownUser validation flow](https://github.com/queueit/KnownUser.V3.Python/blob/master/Documentation/KnownUserFlow.png)
-
- 1. User requests a page on your server
- 2. The validation method sees that the has no Queue-it session cookie and no `queueittoken` and sends him to the correct queue based on the configuration
- 3. User waits in the queue
- 4. User is redirected back to your website, now with a `queueittoken`
- 5. The validation method validates the `queueittoken` and creates a Queue-it session cookie
- 6. The user browses to a new page and the Queue-it session cookie will let him go there without queuing again
-
-## How to validate a user
-To validate that the current user is allowed to enter your website (has been through the queue) these steps are needed:
-
- 1. Providing the queue configuration to the KnownUser validation
- 2. Validate the `queueittoken` and store a session cookie
+Before getting started please read the [documentation](https://github.com/queueit/Documentation/tree/main/serverside-connectors) to get acquainted with server-side connectors.
 
+Connector was developed and verified with Python v.2.7 and Django v.1.8. Please reach out to us if you are using another web framework, so we add it to the supported providers.
 
-### 1. Providing the queue configuration
-The recommended way is to use the Go Queue-it self-service portal to setup the configuration. 
-The configuration specifies a set of Triggers and Actions. A Trigger is an expression matching one, more or all URLs on your website. 
-When a user enter your website and the URL matches a Trigger-expression the corresponding Action will be triggered. 
-The Action specifies which queue the users should be send to. 
-In this way you can specify which queue(s) should protect which page(s) on the fly without changing the server-side integration.
-
-This configuration can then be downloaded to your application server. 
-Read more about how *[here](https://github.com/queueit/KnownUser.V3.Python/tree/master/Documentation)*.
-
-### 2. Validate the `queueittoken` and store a session cookie
-To validate that the user has been through the queue, use the `KnownUser.validateRequestByIntegrationConfig()` method. 
-This call will validate the timestamp and hash and if valid create a "QueueITAccepted-SDFrts345E-V3_[EventId]" cookie with a TTL as specified in the configuration.
-If the timestamp or hash is invalid, the user is send back to the queue.
-
+You can find the latest released version [here](https://github.com/queueit/KnownUser.V3.Python/releases/latest)
 
 ## Implementation
 The KnownUser validation must be done on *all requests except requests for static and cached pages, resources like images, css files and ...*. 
@@ -116,29 +75,9 @@ def index(request):
         # This was a configuration error, so we let the user continue
         print stdErr.message        
 ```
-### Protecting ajax calls
-If you need to protect AJAX calls beside page loads you need to add the below JavaScript tags to your pages:
-
-```
-<script type="text/javascript" src="//static.queue-it.net/script/queueclient.min.js"></script>
-<script
- data-queueit-intercept-domain="{YOUR_CURRENT_DOMAIN}"
-   data-queueit-intercept="true"
-  data-queueit-c="{YOUR_CUSTOMER_ID}"
-  type="text/javascript"
-  src="//static.queue-it.net/script/queueconfigloader.min.js">
-</script>
-```
-
-## Alternative Implementation
-
-### Queue configuration
-
-If your application server (maybe due to security reasons) is not allowed to do external GET requests, then you have three options:
 
-1. Manually download the configuration file from Queue-it Go self-service portal, save it on your application server and load it from local disk
-2. Use an internal gateway server to download the configuration file and save to application server
-3. Specify the configuration in code without using the Trigger/Action paradigm. In this case it is important *only to queue-up page requests* and not requests for resources. 
+## Implementation using inline queue configuration
+Specify the configuration in code without using the Trigger/Action paradigm. In this case it is important *only to queue-up page requests* and not requests for resources. 
 This can be done by adding custom filtering logic before caling the `KnownUser.resolveQueueRequestByLocalConfig()` method. 
 
 The following is an example (using Django v.1.8) of how to specify the configuration in code: