<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On 31 Oct 2016, at 17:10, Muse M via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Are there any plans to create new standard of IAP that design to reduce complexity and improve performance?<div class=""><br class=""><div class=""><a href="http://tutorials.jenkov.com/iap/why-http2-and-websockets-are-not-enough.html#websockets-and-http2" class="">http://tutorials.jenkov.com/iap/why-http2-and-websockets-are-not-enough.html#websockets-and-http2</a><br class=""></div></div></div></div></blockquote><br class=""></div><div>I think the initial focus is likely to be on those protocols that are currently being used by other languages and environments, to bring parity in the implementation. These will build upon low level sockets and/or TCP and UDP streams, which would be necessary to contemplate implementing higher level protocols that aren't derivatives of HTTP.</div><div><br class=""></div><div>Alex</div><br class=""></body></html>