LÖVE

zorg wrote: ↑Sat May 19, 2018 7:56 pm
And again, you don't need to do anything yourself regarding Enet, it's bundled into löve, like how luasocket is. You just

Code: Select all

local enet = require 'enet'

and it works.

-- server.lua
sock = require "sock"

function love.load()
    -- Creating a server on any IP, port 22122
    server = sock.newServer("*", 22122)

    -- Called when someone connects to the server
    server:on("connect", function(data, client)
        -- Send a message back to the connected client
        local msg = "Hello from the server!"
        client:send("hello", msg)
    end)
end

function love.update(dt)
    server:update()
end

zorg wrote: ↑Sat May 19, 2018 8:09 pm 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.

zorg wrote: ↑Sat May 19, 2018 8:09 pm 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.

require "enet"

local enet = require "enet"

4aiman wrote: ↑Sat May 19, 2018 8:25 pm 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 answers with an IP:port of another server to connect to and creates it (the new server)
- the client then disconnects from the main server and connects to the given IP:port where it can easily get an update of any size
- upon completion, the client can re-connect to the main server
That ^ by no means is a perfect way to get some huge data, but it has worked for me so far

zorg wrote: ↑Sat May 19, 2018 7:00 pm

SmartGlassesMan wrote: ↑Sat May 19, 2018 6:48 pm Thanks for the reply. That's helpful information.

No it's not, when it gets misinterpreted.

ivan wrote: ↑Sun May 20, 2018 4:58 am
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).

SmartGlassesMan wrote: ↑Sat May 19, 2018 8:30 pm

zorg wrote: ↑Sat May 19, 2018 8:09 pm 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 think that worked to get past the first error.

I changed the following line in sock.lua

Code: Select all

require "enet"

to

Code: Select all

local enet = require "enet"

The server code in the above post now seems to run without any errors. Certainly no errors thrown yet.

Now, if I can just get past the client code error I'm getting.

Thanks again for your help.