[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] plan for ECF 3.4 final days
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Thu, 21 Oct 2010 00:54:55 +0200
- Delivered-to: firstname.lastname@example.org
- 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; b=JrPgyjsRJ1gDcwK/rYlc7hcu+1o52DO140XBH4T9RDSI24vo2rGelN7p32BBn+Umdd HeEPSfUp2LaTlb3gkC2bzQP1reOQ5gQq6XOvFKlHOCZ7osktbalvdUgBFzGeIJ+i9mvd vZNZMjZfo4PknlKqOnAHm70AgjYa5sm2K4iuA=
Particularly see the Twitter test code issue ...it's going wrong for what looks (to me) like some changes in the twitter service, or the account access or something else. In any event, please assign the bug to yourself if you
Twitter changed its user/password login and now we need to go through the oAuth protocol. This is all fine and dandy but is looks like quite some work to get to know oAuth and how to let it sing with the REST services.
I have found a nice library  called Scribe that aids in getting request and response tokens in place but this will not be done before 3.4 is released.
I suggest to get rid of the failing tests for now since they do not prove that the REST services are not working, only that we are addressing twitter in an unsupported way.
ecf-dev mailing list