Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates
 209.85.220.17 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=f0AYlJmTe1CJPO7XOw5uqp6Gu9jQsNP7NY+ROT9TEMSUA5Ds22vk6pRsd3+KiJt+3j
         bJJIs7ntiYCgt9bv5Bs/2ROwzSQlIMBlMpqe3ge0q00KWaO3iYybkV4USX41KsqkSMOL
         +5eHViUZ2W2CPfgRG2nWfBg6xYqqhxAPIGgQA=
MIME-Version: 1.0
In-Reply-To: 
 <30DB6ACF50A0A3439F39EFEB1C52E166078F22F7@nets13ja.ww300.siemens.net>
References: <c7fc82820902140838o1730a5ceta0628042344f21ad@mail.gmail.com>
	 <30DB6ACF50A0A3439F39EFEB1C52E166078F22F7@nets13ja.ww300.siemens.net>
Date: Mon, 16 Feb 2009 00:27:50 +0200
Message-ID: <c7fc82820902151427w69d767cbwbd9e8e4ce66d8156@mail.gmail.com>
Subject: Re: Twitter RESTful API
From: Vassil Dichev <vdichev@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> 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: apachedick@esmecloudserverapache.dickhirsch.staxapps.net/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.