The new 2.0 version provides an alternative API to the __call
method :).
http://wiki.github.com/jmathai/twitter-async#usage_and_examples
On Nov 1, 3:21 pm, Michael Mokrysz wrote:
> Thanks to both of you, having taken a better look at epitwitter's code
> I'd have to agree that's it's best to swit
I pushed the 2.0 version of the library to Github and it includes
quite a few changes.
Docs:
http://wiki.github.com/jmathai/twitter-async
Release Notes:
http://wiki.github.com/jmathai/twitter-async/twitter-async-20-release-notes
# Added a new (preferred) API
You can now use get, post, delete, ge
I think it will benefit all users of the library to document the
method names for every call. While it's somewhat trivial to determine
the method names it still required just an ounce of brain power. That
ounce should be save for other tasks :).
It's been on my todo list to document them all, b
For PHP, there is a pecl extension.
--
A K M Mokaddim
http://talk.cmyweb.net
http://twitter.com/shiplu
Stop Top Posting !!
বাংলিশ লেখার চাইতে বাংলা লেখা অনেক ভাল
Completely agreed with Michael there. I'm not for a minute suggesting
Abraham's library is any less in value, I just come to appreciate the
nature in which jmathai went about creating the library and it just
seemed to be more 'natural' to work with.
Not to mention as Michael said - you have
Thanks to both of you, having taken a better look at epitwitter's code
I'd have to agree that's it's best to switch. I still like to be able
to pretty much copy and paste urls from the documentation rather than
having think how to convert it into the (albeit ingenious) conversion
method EpiTwitter
+1
I too started with Abraham's, but as you pointed out, that project is
more or less stagnant and Abraham is working on other things. Totally
understandable.
Jmathai's library is technically very sound, extremely well thought
out and continuously being improved. Moreover, jmathai is ver
I much prefer using http://wiki.github.com/jmathai/twitter-async
Scott.
On 1 Nov 2009, at 19:57, Michael Mokrysz wrote:
>
> Hi,
>
> I've been messing around with the API for a while now and I've been
> wondering whether there's any particular consensus over the best
> library to use with PHP? U