Secondly, the request-response nature of HTTP is often cited as one of the limitations for IoT use-cases as it does not match the event-driven nature of applications that are common in the Wireless Sensor Networks.[1][2][12] To overcome this shortcoming while keeping a focus on fostering integration with the Web, several authors have suggested the use of HTML5 WebSockets either natively or through the use of translation brokers (e.g., translating from MQTT or CoAP to WebSockets).[4][6][5][13] This complements the REST API of things with a publish subscribe mechanism that is largely integrated with the Web eco-system.