++ I only recommend EpiTwitter to folks as a PHP library now, ++ It's solid.
On Sat, Sep 4, 2010 at 6:15 PM, Scott Wilcox <[email protected]> wrote: > Haha, that can only lead to a better experience for the end users. For what > its worth, I only recommend EpiTwitter to folks as a PHP library now, and > quite the volume of people at that! > > Shows you're doing something right! :) > > Scott. > > On 4 Sep 2010, at 23:10, jmathai wrote: > > > Thanks Scott :). The same sweetness will be added to my fork of > > Twilio and Facebook's library as well :). > > > > I think my goal in life is to add asynchronous-ness to all php > > libraries :). > > > > On Sep 4, 1:31 pm, Scott Wilcox <[email protected]> wrote: > >> That's a fantastic addition to an already great library. > >> > >> Great work! > >> > >> On 4 Sep 2010, at 21:22, jmathai wrote: > >> > >> > >> > >>> The twitter-async library on github now lets you easily view a > >>> sequence diagram of calls. This is specifically useful when you're > >>> making multiple calls asynchronously. Here's a sample output (looks > >>> better with fixed width font). > >> > >>> http://wiki.github.com/jmathai/twitter-async/#sequence > >> > >>> (http://api.twitter.com/1/direct_messages.json:: code=200, > >>> start=1283577305.2462, end=1283577305.5109, total=0.264562) > >>> > [====================================================================================================] > >>> (http://api.twitter.com/1/users/suggestions.json:: code=200, > >>> start=1283577305.2726, end=1283577305.3871, total=0.114419) > >>> [ ============================================= > ] > >>> (http://api.twitter.com/1/statuses/public_timeline.json:: code=200, > >>> start=1283577305.2731, end=1283577305.4195, total=0.146262) > >>> [ ======================================================== > ] > > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
