LÖVE

I should be more clear in my documentation.. connect and disconnect only work when a handshake is set.

I'm sure this is a stupid question, but what should said handshake be? Just a string that both ends share?

UPDATE: Answered my own question. Thanks.

Update!

v0.03 changelog:

• You can now create multiple instances of server and client, syntax:

  Code: Select all

  newserver = server(<same arguments as Init>)
  newclient = client(<same arguments as Init>)

• Binary packing fixed (thanks to Crokoking for pointing that out)

Another update. Everything has moved to the lube table and to one file.
So: WARNING BACKWARDS INCOMPATIBLE!!

That's why the old one is still available.

Also:
Start on Easy mode, will probably not work as well as it should, but it works. Easy mode consists of 1 setup command, and only updates after that, it auto-synchronizes a table. (uses a user-supplied compression and decompression function).

Hi I didn't read all the discussion here, but I have a suggestion:

Integration of MYSQL comunication. Like: Logging in, sending requests, recieving Data without the need of reading the protocols.

Sparx wrote:Hi I didn't read all the discussion here, but I have a suggestion:

Integration of MYSQL comunication. Like: Logging in, sending requests, recieving Data without the need of reading the protocols.

For what do you need that?! If you feel the need to communicate with a MySQL database you can always use a php script in the middle. A lib to work with SQLite would be way better but I think both have not much to do with this discussion

you can always use a php script in the middle.

Much more secure too.

Someone can write a protocol to be used with LUBE, but I think nobody volunteers to do that. SQL in LÖVE: see the issue tracker, I though of that before.

So if mr nobody does it in the next few month, then i think im going to do that myself.

Found a mistake in LUBE.lua line 328:

return self.socket:sendto(data, rcpt, lube.lube.clients[rcpt])

should be
return self.socket:sendto(data, rcpt, lube.clients[rcpt])


Is it possible to setmore than 1 connection? I guess not... that should be implemented (perhaps the lube.client:connect could return a connection ID which will be passed as parameters to all the other functions)

Oops, search & replace did too much
Didn't run into any problems while testing, but I probably just skipped that function