HTTP services are the main arteries by which the API travels. From an OpenInsight perspective, the journey begins with the entry point service and then passes the call onto the next HTTP service in the path order until the end point service is reached (or an unexpected situation occurs as explained above.) In order for these HTTP services to work properly they must follow a consistent design pattern which will be explained here.

  • No labels