Github user mitchell852 commented on a diff in the pull request:
https://github.com/apache/incubator-trafficcontrol/pull/278#discussion_r100897910
--- Diff: docs/source/overview/introduction.rst ---
@@ -15,14 +15,34 @@
Introduction
============
-Traffic Control is a control plane for a CDN, which includes all of the
components mentioned in the CDN Basics section, except for the Log File
Analysis System. The caching software chosen for Traffic Control is `Apache
Traffic Server <http://trafficserver.apache.org/>`_ (ATS). Although the current
release only supports ATS as a cache, this may change with future releases.
+Traffic Control is a caching server control plane application which is
used to aggregate caching servers into a Content Delivery Network (CDN). The
CDN caching software chosen for Traffic Control is `Apache Traffic Server
<http://trafficserver.apache.org/>`_ (ATS). Although the current release only
supports ATS as a cache, this may change with future releases.
Traffic Control was first developed at Comcast for internal use and
released to Open Source in April of 2015. Traffic Control moved into the Apache
Incubator in August of 2016.
-Traffic Control implements the blue boxes in the architecture diagram
below.
+Traffic Control implements the elements illustrated in green in the
diagram below.
-.. image:: traffic_control_overview_3.png
+.. image:: CDN-Traffic-Control.png
:align: center
+
+**Traffic Ops**
+ * `Traffic Ops
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_ops.html/>`_ is
used to configure caching servers and CDN delivery services. It also contains
APIs used to access CDN data.
+
+**Traffic Router**
+ * `Traffic Router
<http://trafficcontrol.apache.org/docs/latest/overview/traffic_ops.html/>`_ is
used to route clients requests to the closest healthy cache by analyzing the
health, capacity, and state of the caching servers and relative distance from
each cache group to the location of the client.
--- End diff --
copy / paste error on the link?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
