At 06:01 13/08/2010, Andreas Raab wrote:
>renderLoginPageOn: html
>
> "Set up the callback url for Twitter to return to"
> callback := WAActionCallback on: [self twitterCallback].
> url := html actionUrl copy addField: (html callbacks store:
> callback).
>
> "We need the host and the scheme here; the scheme is guesswork"
> urlString := '
http://', host, '/', url asString.
> oauthParams at: 'oauth_callback' put: urlString encodeForHTTP.
>
>and then later the callback is passed to Twitter and the user sent back
>to the app. This works, but I'm wondering if that's the right thing to
>do, and if not, how one would set up and register such a callback url
>outside of rendering.
Hi Andreas,
Thank you for your contribution that I'm reusing successfully on a
deployed web app for my ESUG demo.
FYI, I just had a minor trouble with the oAuthCallbackUrl that you
mention above. I just changed it to
oAuthCallbackUrl := url asString. "Twitter-Squeak-ar.2"
It now works on the remote server, but no more on the localhost.
Hoping this helps,
Cheers,
Reza
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
