Well they are all open source, so just fork it for your needs, stripping out the classes you don't wont.
I would say that generally you implement consumer and provider in same library because it's easy to then verify your own client/server implementations in tests against each other, and there's a large amount of shared implementation between both roles. On Tue, Apr 21, 2009 at 11:51 PM, Kevin Mandeville <kvnsmo...@gmail.com>wrote: > > Am I mistaken about the madgex library that it only supports POST and > GET? also most of these other .Net libraries seem like major overkill > when all I need is a client side library. It's not often that a single > developer would need both server side and clientside libraries. Is > there any way to separate them? > > On Apr 21, 2009, at 4:41 AM, "chris.s.ad...@googlemail.com" < > chris.s.ad...@googlemail.com > > wrote: > > > > > Hi Alex, > > > > If you have any suggestion on what to do with our OAuth Library > > (Madgex http://code.goole.com/p/oauth-dot-net/) I'd like to hear about > > it. Any ideas on what it's lacking / needing always welcome. > > > > Chris > > > > On Apr 21, 12:09 am, Alex Henderson <bitterco...@gmail.com> wrote: > >> OAuthBase.cs is a buggy/flawed implementation - I would suggest > >> looking at > >> one of these 3 options for OAuth on the .Net Framework - also check > >> out > >> Owen's experience with the OAuthBase.cs class here, which you might > >> find > >> interesting: > >> > >> http://bgeek.net/2009/03/03/oauth-mvcnet-revisited/ > >> > >> There are a few options I know of at current: > >> > >> Madgex's OAuth Library - > http://lab.madgex.com/oauth-net/&http://code.google.com/p/oauth-dot-net/ > >> DevDefined Tools OAuth Library -http://code.google.com/p/devdefined- > >> tools/wiki/OAuth > >> DotNetOpenAuth (OpenId and OAuth) -http://github.com/AArnott/ > >> dotnetopenid/tree/master > >> > >> None are ideal at this stage IMO (I wrote the second one and have > >> dug around > >> the code in the other two) - but they are all better starting > >> points then > >> OAuthBase.cs. > >> > >> Cheers, > >> > >> - Alex > >> > >> On Tue, Apr 21, 2009 at 9:45 AM, Kevin M <kvnsmo...@gmail.com> wrote: > >> > >>> I'm having an issue where I'm POSTing data to a page using x-www- > >>> form- > >>> urlencoded parameters. The string I'm posting looks just like a > >>> normal > >>> query string and I'm writing this data directly to the Stream > >>> obtained > >>> from the HttpWebRequest object. > >> > >>> So my problem lies directly with the GenerateSignatureBase method > >>> call. Since this extra data is posted in the body and not included > >>> in > >>> the query string, the call to GenerateSignatureBase does not take > >>> these parameters into account. The server side code (Java library) > >>> does take these posted parameters into account when creating the > >>> signatureBase (as it should based on the spec). > >> > >>> Any ideas? I've tried hacking it a bit by appending my data to the > >>> URL > >>> as a query string (will not work long term) and not posting the data > >>> in the body and that worked, sort of. But this is not the > >>> appropriate > >>> way to do this. > >> > >>> Kevin M > >> > >> > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
