Thanks Paul,
I'll log your message here as an issue and see what I can do. And as
far as WebException is concerned,
you can just cast its Response property to HttpWebResponse rather than
go digging in the header. That's exactly what I do to retrieve the
root's Response object. So that means you
Hi Paul,
What is tweet#? Can you let us know more about it?
On Tue, Mar 3, 2009 at 2:28 PM, Paul Kinlan paul.kin...@gmail.com wrote:
Hi Daniel,
I am using tweet# a lot, and it would be good if you catch the 503 error
status on the rate limited requests (including the Retry-After header in
Hi Burhan,
Tweet# is a .Net twitter client API. It has been developed in a fluent
interface style so you construct your twitter requests in a manner that you
can read from left to right.
For example I use it to search:
var result =
Thanks for the feedback; right now you can get at the response in
instance.Root.Response (where instance is your FluentTwitter query),
which will give you the instance of the last response returned. I'll
look at this closer (unless you have a patch already of course).
Daniel
On Mar 3, 11:28 am,
Thats pretty much where I am handling the 503, my client code intercepts the
exception and then inspects the header. The other thing I noticed, and it
is probably not best on this list is that you use WebRequest which raises a
WebException, and you can't get the 503 out of it easily (at least
