An API so slow you die before getting a response.
Person 1: Hey, have you used GreenCobalt's API?
Person 2: *dead because it took so long to respond*
9👍 3👎
found usually on blackberry curve (non-3G) devices when trying to login to twitter or other apps, especially in slow internet connection/EDGE areas.
It is a misnomer why this error message is displayed and not simply: no connection to server. Perhaps reference is being made to the particular API (-set of programming instructions) that allows twitter and other apps to connect.
It is thought by many to be a product of an under-developed device and/or network.
Blackberry screen error: "Twitter failed to connect. You have reached your API limit."
Love Birds/The perfect symbol of love!
Their love is as strong as Api x Vengy
A bloody mess of macros, typedefs and compile errors.
WHY AM I ALWAYS GETTING ERRORS? WHO INVENTED THE WINDOWS API?!
An API far superior to any other API (including Bunny's).
I use GreenCobalt's API for all my data sources because it's much superior to any other API!
Lifecycle API is a funny idiosyncratic name, invented by some young IT folks, to try to politically justify that the API is only responsible of the lifecycle of the Data itself but not of the data that flows through it, and that the API is not doing what it actually does i.e. Create Read Update Delete operations.
A funny API that was meant to be a global integration layer for content management, and resulted to be a mapping read only of four data fields (i.e. just the Read part of the CRUD).
It was not politically possible to call it global content API or global archiving API, it was not possible to call it with the original name of the API that it was copied and stolen from and therefore the funny name came along.
Lifecycle API is not an overlay/platform API, but just a CRUD interface on GAP