RTM requests and caching

[Eric Wendelin]

It looks like lately (last few weeks or so) I've seen different
behavior related to how RTM retrieves task lists. Could be other
functionality but I haven't tested.

If one calls rtm.tasks.getTaskList and then makes an API call to
perform some change to a task (complete, delete, etc) and then shortly
thereafter (within a couple minutes) calls rtm.tasks.getTaskList the
response will not reflect changes.

I have a feeling that this is because RTM is caching static responses
to requests it has seen in a given window and sending the cached
response. I'm guessing this is what may have "fixed" the API slowness
we were all seeing a month ago. It's a really smart idea, actually,
since getting task lists is probably by far the #1 most called API
method.

Anyway, I'm hoping someone can confirm this for me so I can make
changes to my RTM application to accommodate.

Thanks,
Eric Wendelin

[Omar Kilani]

Hey Eric,

There was some caching enacted on specific API keys as a temporary
measure -- this particular caching is now disabled.

We've just deployed a new system for the API which should speed up
everyone's requests (we're seeing up to 100x improvements in response
times) and also stop misbehaving API applications from affecting the RTM
service (and other API users).

You shouldn't have to make any changes to your application to benefit
from these new changes. :)

Thanks!

Regards,
Omar

[Eric Wendelin]

Yes, I'm seeing things back to normal, AND the speed improvements :)

I'm sure you guys get spammed with a ton of requests to certain APIs.
Good work.

Thanks a bunch for the update!

Cheers,
-Eric