On Wed, Apr 7, 2010 at 5:30 PM, Raffi Krikorian <ra...@twitter.com> wrote: > i would love to know how we can make oauth simpler for people. should we > provide better documentation? examples? libraries? > >
Here is the Classic ASP code (by Ariel Saputra) that my site uses: ---- function asp_twitter_update(strMsg,strUser,strPass) dim oXml,strFlickrUrl strFlickrUrl = "http://twitter.com/statuses/update.xml" set oXml = Server.CreateObject("Msxml2.ServerXMLHTTP.3.0") oXml.Open "POST", strFlickrUrl, false, strUser, strPass oXml.setRequestHeader "Content-Type", "application/x-www-form-urlencoded" oXml.Send "status=" & server.URLencode(strMsg) asp_twitter_update = oXml.responseText Set oXml = nothing end function ---- Whenever a visitor to my site posts a new classified ad, the Classic ASP script automatically, invisibly, seamlessly sends out a tweet through the site's Twitter account that announces the new ad. Users need not have a Twitter account of their own and need not know or understand anything about Twitter, because the tweets are sent without their having to do anything other than submit their classified ad via my site's Classic ASP form. It was so easy to incorporate that bit of code into my form! I would be grateful for suggestions of how to accomplish the same thing with Classic ASP and oauth. Actually, to do this for Classic ASP/oauth is something of a holy grail for those of us who use Classic ASP; as there are lots of us who are concerned about this issue.