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.161.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=LoKQuLLCaFz97Ea0qkVYbiFBj15OtEBbEAPIQPnLGr0vOXpR3cHJ9Nwtq+BqZU5jni
         SvgjFbmH53bL+bEeg5nb1BKMKEYPxbrB9PQithSZiS2B9LReN04pEy3DddH1aZ+QP06f
         Cibuo2URVnynwcLyL35pJGU9tG030ZCGH+h+Y=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <AANLkTimuWpZNNr9WRPmXRuZpsnki-UA_1oxbIQMo3_oz@mail.gmail.com>
References: <AANLkTimg5nGlfWVc13Ri5zsGJZrtLvmkJ6PIgHAB-eZ9@mail.gmail.com>
	 <AANLkTik8XPk9PRSbp0eK1lEI3X4UhiqV0NvpHTiNKbE0@mail.gmail.com>
	 <AANLkTimuWpZNNr9WRPmXRuZpsnki-UA_1oxbIQMo3_oz@mail.gmail.com>
Date: Wed, 26 May 2010 08:27:32 +0300
Message-ID: <AANLkTinLZLaOKZplcJOMfX_vuJrlPf_Ww0HR60kyZYr7@mail.gmail.com>
Subject: Re: Twitter api Up-to-Date?
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Right, the Twitter API ignores additional parameters because the few
Twitter clients that I've tested didn't use them. Next item on the
todo list.

And yes, home_timeline is new (since after Twitter introduced
retweets), so it wasn't there when the API was developed. I guess
there's some catching up to do.

By the way, good call on adding the missing functionality in there!

Vassil


On Tue, May 25, 2010 at 8:13 PM, Richard Hirsch <hirsch.dick@gmail.com> wro=
te:
> I added the two lines (I'll commit them tomorrow) and yu can now
> receive messages via tweetdeck.
>
> Next problem: =A0since-id needs to be used to make the follow-up query
>
> 93.82.138.33 - h [25/May/2010:17:09:51 +0000] "GET
> /twitter/statuses/home_timeline.xml?count=3D100&since%5Fid=3D7673
> HTTP/1.1" 200 14002
>
> D.
>
> On Sun, May 23, 2010 at 1:22 PM, Richard Hirsch <hirsch.dick@gmail.com> w=
rote:
>> This might actually work if we added the following lines to the
>> TwitterAPI.scala file.
>>
>> case Req(ApiPath ::> "statuses" ::> "home_timeline", this.method,
>> GetRequest) =3D> userTimeline
>> case Req(ApiPath ::> "statuses" ::> "home_timeline" ::> last,
>> this.method, GetRequest) =3D> () =3D> userTimeline(last)
>>
>> One problem is that the returned # of messages is hardcoded in scala
>> with "20" whereas the latest twitter api has the ability to pass the
>> value with the 'count' parameter.
>>
>> D.
>>
>> On Sun, May 23, 2010 at 8:47 AM, Richard Hirsch <hirsch.dick@gmail.com> =
wrote:
>>>
>>> I just finished using Tweetdeck to access ESME (details here: http://st=
atus.net/2010/05/21/tweetdeck-supports-statusnet)=A0 and I noticed that we =
can send send messages via the twitter api but the personal timeline appear=
s to be broken:
>>>
>>> 62.47.190.106 - h [23/May/2010:06:41:12 +0000] "GET /twitter/statuses/r=
eplies.xml?count=3D100 HTTP/1.1" 200 2744 "app:/TweetDeck.swf" "Mozilla/5.0=
 (Windows; U; de-DE) AppleWebKit/526.9+ (KHTML, like Gecko) AdobeAIR/1.5.3"
>>> 62.47.190.106 - h [23/May/2010:06:41:33 +0000] "GET /twitter/statuses/h=
ome_timeline.xml?count=3D100 HTTP/1.1" 404 276 "app:/TweetDeck.swf" "Mozill=
a/5.0 (Windows; U; de-DE) AppleWebKit/526.9+ (KHTML, like Gecko) AdobeAIR/1=
.5.3"
>>>
>>> D.
>>
>