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, 3 insertions, 2 deletions

diff --git a/samples/Consumer/App_Code/InMemoryTokenManager.cs b/samples/Consumer/App_Code/InMemoryTokenManager.cs
index 83c45bd..edd3a9d 100644
--- a/samples/Consumer/App_Code/InMemoryTokenManager.cs
+++ b/samples/Consumer/App_Code/InMemoryTokenManager.cs
@@ -8,6 +8,7 @@ using System;
 using System.Collections.Generic;

 using System.Diagnostics;

 using DotNetOAuth.ChannelElements;

+using DotNetOAuth.Messages;

 

 public class InMemoryTokenManager : ITokenManager {

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

@@ -35,8 +36,8 @@ public class InMemoryTokenManager : ITokenManager {
 		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;

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

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

 	}

 

 	/// <summary>