This is indeed an option, but I don't really know what to call that doesn't either involve creating unnecessary NetServices or creating unnecessary sockets. Unless this is as good as it gets. I was hoping for better.
Go was a logical choice mostly down to the fact that it's incredibly easy to prototype in, and the project *is alpha* at this stage. Once specced properly, I would like to think that we will get more implementations in different languages. Incidentally, I was able to use gomobile/gobind to generate an Yggdrasil.framework which I was able to link against for building the iOS app / networkextension and make calls directly to from Swift. It wasn't difficult to do but it is rough around the edges - it does work at least. :-) I'm hoping someone from Apple hears our pleas for AWDL in the right places though - it's the missing piece that would really make this feel *magic*. Rgds, Neil On 22 Feb 2019, at 16:36, Jens Alfke <j...@mooseyard.com<mailto:j...@mooseyard.com>> wrote: You could use CGo to call some glue code written in those languages. [Off-topic, but: This project looks very interesting, but my heart sank when I saw it’s written in Go. It’s not a bad language, but it’s awkward to integrate into anything else, esp. on mobile, because of its insistence on doing everything differently, from heaps to threading to stack frames. (I’ve written quite a lot of Go in the past, so I’m not speaking from ignorance here...)]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com