Third Party Developer Blog

Hello space developers, As stated previously, error limiting in ESI has been imminent since August 29th. Starting after downtime on Monday, October 2nd, Team Tech Co. will officially turn on the ESI error limit functionality. If you're worried about invoking the wrath of the error limiter, you still have the weekend to check your application and clean up your code (you are backing off when you get errors, right?). The way to know if your software will be error limited after Monday is to look for the HTTP header X-Esi-Error-Limited in responses coming from ESI. There are two HTTP headers being returned from ESI that will help ensure your app never hits the error limit. These are X-Esi-Error-Limit-Remain and X-Esi-Error-Limit-Reset. X-Esi-Error-Limit-Remain will let you know how many more errors you can make within the window of time defined by X-Esi-Error-Limit-Reset, which ... read more

This blog post is part of a series of blogs examining best practices for ESI development. Each blog will be published on the 8th of each month during the journey towards XML API and CREST’s termination date. The legacy APIs will be terminated on May 8th, 2018, or earlier if metrics signal a trivial level of usage. This blog will cover the concept of concurrent programming and how to use this model of programming to improve your software's performance while pulling data from ESI. If you are already familiar with the concept of concurrent programming here is a ESI pagination TLDR: Use the X-Pages header returned from paginated ESI endpoints to determine how many calls are needed to get all data from a given endpoint. Prerequisites This blog includes examples of Linux commands as well as Python code, therefore if ... read more