From f35eb186d62ca2f77add1ebde8c70495f9eeea1b Mon Sep 17 00:00:00 2001
From: toepp <toepp@lokale-internetwerbung.de>
Date: Wed, 31 Aug 2022 11:03:31 +0200
Subject: [PATCH] removed commented imports and added a better description

---
 src/access_token.rs | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/access_token.rs b/src/access_token.rs
index 1ca1d0f..af83b5d 100644
--- a/src/access_token.rs
+++ b/src/access_token.rs
@@ -1,14 +1,17 @@
-//! pseudo authenticator for use with plain access tokens
+//! pseudo authenticator for use with plain access tokens.
+//! If you use a specialized service to manage your
+//! OAuth2-tokens you may get just the fresh generated
+//! access token from your service.
+//! The intention behind this is that if two services using the
+//! same refresh token then each service will invalitate the
+//! access token of the other service by generating a new token.
 use crate::error::Error;
 use crate::types::TokenInfo;
 use hyper::client::connect::Connection;
-// use hyper::header;
 use http::Uri;
-// use serde::{Deserialize, Serialize};
 use std::error::Error as StdError;
 use tokio::io::{AsyncRead, AsyncWrite};
 use tower_service::Service;
-// use url::form_urlencoded;
 
 /// the flow for the access token authenticator
 pub struct AccessTokenFlow {