<div dir="ltr">Don't know if I'm late to this conversation. I have been using the <a href="http://perfect.org">perfect</a> platform for server-side swift. My understanding was it is the most robust platform, but I'm using it because my boss said so. I haven't had any problems and I'm finding the community around it is growing solid. If you want to give it a try, <a href="https://medium.com/@abjurato/swift-perfect-mustache-and-postgresql-on-heroku-48d483fe8489#.4z8r26myq">this tutorial</a> is pretty solid.<div><br></div><div>Thanks,</div><div>Fareed</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 8, 2016 at 1:08 PM, Gerard Iglesias via swift-users <span dir="ltr"><<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Jens,</div><div><br></div><div>I have to say that I am far from an expert in low level network coding, even if I started using Distributed object in 93 with NeXTStep, and I can build network connection with the basics, listen, bind, accept ... There is an interesting network code in swift with these basics on the IBM swift playground.</div><div><br></div><div>I wonder what kind of limitations are no longer relevant ?</div><div><br></div><div>And I found CocoaAsync very interesting to read because of the intensive use of GCD</div><div><br></div><div>And maybe it would be interesting to know who use what today with swift to put a server or a client in use?</div><div><br></div><div>Regards<br><br>Gérard </div><div><div class="h5"><div><br>Le 3 mai 2016 à 23:03, Jens Alfke <<a href="mailto:jens@mooseyard.com" target="_blank">jens@mooseyard.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><br><div><blockquote type="cite"><div>On May 3, 2016, at 12:46 PM, Gerard Iglesias <<a href="mailto:gerard_iglesias@me.com" target="_blank">gerard_iglesias@me.com</a>> wrote:</div><br><div><div style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">A good reading </div><div style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><div style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="https://github.com/robbiehanson/CocoaAsyncSocket" target="_blank">https://github.com/robbiehanson/CocoaAsyncSocket</a></div></div></blockquote></div><br><div>This is highly Mac/iOS-specific code, so it doesn’t make sense for applications targeted at servers.</div><div><br></div><div>Also, I’ve used CocoaAsyncSocket and it’s IMHO greatly overcomplicated for what it does. There is a LOT of code in there, and a fair amount of the complexity seems to be to work around obsolete limitations of iOS networking that are no longer relevant.</div><div><br></div><div>—Jens</div></div></blockquote></div></div></div><br>_______________________________________________<br>
swift-users mailing list<br>
<a href="mailto:swift-users@swift.org">swift-users@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><a href="http://www.FareedQ.com" target="_blank">www.FareedQ.com</a><div>Twitter @IAmFareedQ</div></div></div>
</div>