StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POOAuth - lexicographical byte value ordering in c#
primarykey
Id
839429
data
AcceptedAnswerId
0
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-08T11:38:24.580
FavoriteCount
0
LastActivityDate
2010-09-02T03:35:57.563
LastEditDate
LastEditorUserId
0
OwnerUserId
101980
ParentId
0
PostTypeId
1
Score
1
ViewCount
1962
LastEditorDisplayName
text
Body
I have written an Service Provider implementation for OAuth and one of the Devs found a bug in the way the implementation was ordering query parameters. I totally missed the <a href="http://oauth.net/core/1.0/#anchor14" rel="nofollow noreferrer">lexicographical ordering</a> requirement in the OAuth spec and was just doing a basic string sort on the name value parameters Given the following URI request from the consumer: <pre><code>http://api.com/v1/People/Search?searchfor=fl&communication=test@test.com&Include=addresses </code></pre> The resulting signature base should order the parameters as: <pre><code>Include=addresses, communication=test@test.com, searchfor=fl </code></pre> Given the following URI request from the consumer: <pre><code>http://api.com/v1/People/Search?searchfor=fl&communication=test@test.com&include=addresses </code></pre> The resulting signature base should order the parameters as: <pre><code>communication=test@test.com, include=addresses, searchfor=fl </code></pre> Note the case difference in the querystring parameter "include". From what I understand, lexicographical byte value ordering will order parameters using the ascii value and then order asc. Since I = 73 and i = 105, the capital I should be ordered before the lowercase i. I have the following so far: <pre><code>IEnumerable<QueryParameter> queryParameters = parameters .OrderBy(parm => parm.Key) .ThenBy(parm => parm.Value) .Select( parm => new QueryParameter(parm.Key, UrlEncode(parm.Value))); </code></pre> But that will not cover the ascii character by character sort (IncLude=test&Include=test will not sort properly). Any thoughts on how to make an efficient algorithm that will answer this problem? Or how to make the sort case sensitive via ICompare? 
Tags
<sorting><oauth><parameters>
Title
OAuth - lexicographical byte value ordering in c#
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USNick
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POOAuth - lexicographical byte value ordering in c#
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.