Added strong-typed request token message to sample.

This proves that messages can be derived from and tailored to provide type-safe additions where the OAuth protocol permits it.
As can be seen, several more types and members had to be made public for this to work.

1 files changed, 4 insertions, 3 deletions

diff --git a/src/DotNetOAuth.Test/Mocks/InMemoryTokenManager.cs b/src/DotNetOAuth.Test/Mocks/InMemoryTokenManager.cs
index 87d7608..7f8c3b7 100644
--- a/src/DotNetOAuth.Test/Mocks/InMemoryTokenManager.cs
+++ b/src/DotNetOAuth.Test/Mocks/InMemoryTokenManager.cs
@@ -9,6 +9,7 @@ namespace DotNetOAuth.Test.Mocks {
 	using System.Collections.Generic;

 	using System.Diagnostics;

 	using DotNetOAuth.ChannelElements;

+	using DotNetOAuth.Messages;

 

 	internal class InMemoryTokenManager : ITokenManager {

 		private Dictionary<string, string> consumersAndSecrets = new Dictionary<string, string>();

@@ -34,9 +35,9 @@ namespace DotNetOAuth.Test.Mocks {
 			return this.tokensAndSecrets[token];

 		}

 

-		public void StoreNewRequestToken(string consumerKey, string requestToken, string requestTokenSecret, IDictionary<string, string> requestParameters, IDictionary<string, string> responseParameters) {

-			this.tokensAndSecrets[requestToken] = requestTokenSecret;

-			this.requestTokens.Add(requestToken, false);

+		public void StoreNewRequestToken(RequestTokenMessage request, UnauthorizedRequestTokenMessage response) {

+			this.tokensAndSecrets[response.RequestToken] = response.TokenSecret;

+			this.requestTokens.Add(response.RequestToken, false);

 		}

 

 		/// <summary>