PerServ - Understanding acs vs. url

Perserv urls introduce "acs" as a distinct element within a url. Consider the following example url

      http://example.com:00000/00000-00000/dynamic_psd.py?a=1111&b=2222
      |  |   |         | |   | |         | |            | |           |
      |  |   |         | |   | |         | |            | |           |
      +--+   +---------+ +---+ +---------+ +------------+ +-----------+
    protocol    domain    port    auth          path        param(s)
      |                                   |
      |                                   |
      -------------------------------------
                   acs

Fig. 1 ACS links found at right in Port Manager
The auth field is a new addition within Perserv. The acs is the url from protocol to auth and including the final "/".

For your convenience, the acs of every port is listed in the Port Manager. you may copy them for reference or click to activate. What happens when you click is governed by the control.xml entry at passports>> [base_port] >> start.

Applications make use of the acs to communicate. When applications communicate among themselves, they are using the same acs as humans. Merely the path and param(s) differ.