>From what I saw, it is not ""twitter/api" but "twitter" (JSON) or "api" (XML). >Probably have to check the twitter api again to make sure. That means we >don't need a url with two segments but two separate URLs. D.
________________________________ From: Vassil Dichev [mailto:[email protected]] Sent: Sun 2/15/2009 23:27 To: [email protected] Subject: Re: Twitter RESTful API > Just tried twhirl based on this blog from shoutem > (http://blog.shoutem.com/2009/02/14/how-to-setup-shoutem-desktop-app-twhirl/). > Example: Use this as your user: > [email protected]/twitter > > Here are the results from the call - all 404s. I don't know whether the > problem is the "api" in the URL Ah, right, Twhirl works with laconi.ca, which has a twitter-compatible API. I've committed configuration via properties- you should now be able to connect with twhirl if you configure twitter.prefix=api Unfortunately, I still don't see an easy way to configure a URL with several segments, like "twitter/api". Then there's the problem that Twhirl still tries to connect through SSL only, so you need to configure Jetty for SSL or at least use some sort of SSL proxy/tunnel.
