{"action":"opened","issue":{"url":"https://api.github.com/repos/SuperHouse/esp-open-rtos/issues/133","repository_url":"https://api.github.com/repos/SuperHouse/esp-open-rtos","labels_url":"https://api.github.com/repos/SuperHouse/esp-open-rtos/issues/133/labels{/name}","comments_url":"https://api.github.com/repos/SuperHouse/esp-open-rtos/issues/133/comments","events_url":"https://api.github.com/repos/SuperHouse/esp-open-rtos/issues/133/events","html_url":"https://github.com/SuperHouse/esp-open-rtos/issues/133","id":151019381,"number":133,"title":"HTTP client library","user":{"login":"projectgus","id":205573,"avatar_url":"https://avatars.githubusercontent.com/u/205573?v=3","gravatar_id":"","url":"https://api.github.com/users/projectgus","html_url":"https://github.com/projectgus","followers_url":"https://api.github.com/users/projectgus/followers","following_url":"https://api.github.com/users/projectgus/following{/other_user}","gists_url":"https://api.github.com/users/projectgus/gists{/gist_id}","starred_url":"https://api.github.com/users/projectgus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/projectgus/subscriptions","organizations_url":"https://api.github.com/users/projectgus/orgs","repos_url":"https://api.github.com/users/projectgus/repos","events_url":"https://api.github.com/users/projectgus/events{/privacy}","received_events_url":"https://api.github.com/users/projectgus/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-26T01:32:20Z","updated_at":"2016-04-26T01:32:20Z","closed_at":null,"body":"This is related to #132, but I thought it'd warrant its own issue to discuss/track.\r\n\r\nFor a long time I've wanted to include an HTTP client library in esp-open-rtos. Making raw socket requests works for simple actions (apart from obvious problems like #132), but it'd be good to have some wrappers for common HTTP operations.\r\n\r\n* I tried porting a stripped down libcurl, but even stripped down it's not suitable for this size of processor\r\n* mbed has its own C++ HTTPClient library (although I'm not sure where the canonical source for it is), but it's in C++ and fairly mbed-centric so it may not be suitable.\r\n\r\nMost people seem to just DIY on raw sockets for the subset of HTTP they need. We could write our own I guess, it might be of wider interest if it only depends on LWIP."}}