Edited wiki page WhatAreAdaptors through web user interface.
diff --git a/WhatAreAdaptors.wiki b/WhatAreAdaptors.wiki
index 692147b..f15e9dd 100644
--- a/WhatAreAdaptors.wiki
+++ b/WhatAreAdaptors.wiki
@@ -16,4 +16,14 @@
The APIs are designed where you were can ignore pieces you don't need, and only learn them once you need them. This makes the various features separate and orthogonal to each other. To implement a basic Adaptor, you only need to implement two methods know the basics of five different classes. In some ways, five classes may seem like too many, but they all serve an obvious function and you only need one method from each.
-Performance is a concern for the Adaptor Library, but it does come second to ease of use. However, even without giving up how easy the library is to work with, the library has been able to achieve high performance and easily handles millions of documents; we generally expect the GSA or the repository to be the bottleneck.
\ No newline at end of file
+Performance is a concern for the Adaptor Library, but it does come second to ease of use. However, even without giving up how easy the library is to work with, the library has been able to achieve high performance and easily handles millions of documents; we generally expect the GSA or the repository to be the bottleneck.
+
+= Adaptor Architecture =
+
+Adaptors have two main pieces and a third piece for non-public repositories. The two main pieces are a _lister_ and a _retriever_. With just those two pieces the core architecture is formed and a working Adaptor can be created. The third piece performs authorization.
+
+The _retriever_ is an HTTP server that responds to requests for particular documents. When the GSA would like the contents of a document, it sends a request to the retriever and downloads the contents. Documents are identified by a DocId, and it is the retriever's job to get the bytes for the document referenced by a DocId.
+
+The _lister_ informs the GSA that documents exist in the repository. Commonly it will list all the documents in the repository. However, with some Adaptors it doesn't need to list all the documents because the GSA can find the rest through its normal crawling. Once the GSA has been informed about a document via the lister, it will then call the retriever to download the contents.
+
+The authorization piece is provided a list of DocIds and a user, and is given the task of determining which DocIds the the user can access. This is used when the GSA is configured to use it (it is possible to have security in place without it) or when a user points his browser to the HTTP server manually to access the document.
\ No newline at end of file
