I think one reason to have rate-limits on your api and communicate
them to your api consumers is to enforce a proper architecture for
your consumers.
Some developers don't think about the case, what happens if an API is
down OR think it's a good idea to get those 65535 subresources in that
while(true) loop. If there is a rate-limit (like e.g. on
twitter/github) you have to think twice if you really need to do that
request. In my experience we ended up with smarter solutions :).
> --
> You received this message because you are subscribed to the Google Groups "API Craft" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
api-craft+...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/api-craft.
> For more options, visit
https://groups.google.com/d/optout.
--
http://dracoblue.net