{"push_id":3125784120,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"f76daef7907a8e11953ae111b7f928e97c75b9c0","before":"fb9eb2b23fa609f2e0fcec660a0ea91e5953953c","commits":[{"sha":"f76daef7907a8e11953ae111b7f928e97c75b9c0","author":{"name":"Bert Kleewein","email":"7c92651fbcc8626060141c174bdd002aa6ce1a42@users.noreply.github.com"},"message":"POC for adding _async wrappers for InternalClient functions (#28)\n\nThis is one way we could create async wrappers for our code. I like this because:\r\n\r\nAll transport calls run in a background thread, so we never block the main event loop.\r\ntransport callbacks signal the awaiting thread when operations are done by using a Future object. This way the main event loop isn't blocked waiting operations to complete, and we don't need to make a thread that waits for our operation to complete.\r\nasync methods are added to InternalClient with _async suffixes. We could also make InternalClientAsync to hold the async functions, but that seems like it could explode as we add DeviceClientAsync and ModuleClientAsync, and I'm sure we would need to add more.\r\nI've tested this with sending 1000 events in parallel and it seems to do as well as we want. I've also tested that we can still use the client object with Python 2.7 because the code that adds the _async implementations is protected by try/except.","distinct":true,"url":"https://api.github.com/repos/Azure/azure-iot-sdk-python-preview/commits/f76daef7907a8e11953ae111b7f928e97c75b9c0"}]}
{"actor":{"display_login":"BertKleewein"}}