KayleMaster wrote: ↑Fri Jun 01, 2018 1:56 pm Here you go: https://github.com/airstruck/knife/blob ... me/test.md
You can also check out busted.

Thanks!

There aren't a lot of bells and whistles yet, but it gets the job done. Here's the source , I'll add documentation and examples at some point. Hi! I realize that you did all of this free of charge and may not have had the time, but; have you released any of that documentation or those examples yet?...

It's pretty much the same as Windows networking, you've just gotta be super conscious of data usage and dealing with network drop outs. Here's a game I'm working on that is entirely network oriented that is going to be released on mobile platforms: https://love2d.org/forums/viewtopic.php?f=14&t...

Ikroth wrote: ↑Mon May 21, 2018 3:58 pm
Thanks for reporting that, I just pushed a fix that exports enet as a local instead. I didn't like the global style before either. Let me know if you have other issues, I haven't done a full check since 11.0.

Oh, you are welcome. Thanks for writing the library!

Yep, enet and luasocket are cross platform. However, you are still going to need some sort of authentication - which is usually handled through Andoid/iOS (I don't think you can interface with these from Lua/FFI). Good point. Yes, there is much more to networking than just access to a low-level net...

On a side note, you may want to learn about threads as sending some huge data (say, upon connection of a new client which doesn't have any cache stored) will hinder any other message processing. What I did was: - connect to a server, check for content updates - if there are updates, the server answ...

I don't know any sock.lua, but if it's using enet from before 0.11 nightlies, then it might still expect enet to set a global variable (called enet) and expects it to work like that; it doesn't anymore, that was bad coding style. You can check and just edit it so it'll be a file-local instead. I th...

I don't know any sock.lua, but if it's using enet from before 0.11 nightlies, then it might still expect enet to set a global variable (called enet) and expects it to work like that; it doesn't anymore, that was bad coding style. You can check and just edit it so it'll be a file-local instead. Nice...

And again, you don't need to do anything yourself regarding Enet, it's bundled into löve, like how luasocket is. You just local enet = require 'enet' and it works. Ah. There must be something wrong with my sock.lua code then. I got an error about enet being nil, and I went down the path of thinking...

One problem you have to deal with on mobile platforms, but not so much on PC, is roaming - e. g. endpoints moving between WiFi and carrier networks, or other sudden IP address changes, are common on mobile. A good mobile user experience means you have to take this into account. True. Thanks for mak...