Not directly, but you can write getter and setter RPC methods instead. This way you can make sure a client has permission to change or view data based on whatever rules you want. The only reason I went for "methods" rather than "functions" is so you have access to the relevant s...

Not directly, but you can write getter and setter RPC methods instead. This way you can make sure a client has permission to change or view data based on whatever rules you want. The only reason I went for "methods" rather than "functions" is so you have access to the relevant s...

I took a crack at it. https://gist.github.com/airstruck/5e0d0336231cfdefd3f6424afe6e75dc Uses binser for serialization. Should be pretty straightforward, see examples. Everything is synchronous. Define your remote procs as methods of the rpc server object (as rpc:method, not rpc.function), and then...

RPC is a pretty generic technology though; but i'm guessing you need to have a server which gets requests to call procedures, and then return the results to the client(s)? you can just send 1+n messages, first the function name, then the parameters that the function expects, and it will return the ...

Good morning, I'm doing a distributed systems discipline in college ... The first exercise was to create a multiplayer game with sockets. It was easy. My problem is in the second exercise, I need to change the game technology to rpc (remote procedure call), something similar to the Java RMI. Is ther...

Hello developers, first of all, sorry for my bad english :crazy: I'm implementing my first game using love2D called Yoté . My intention is not to show a perfect game, but to contribute in some way with: Multiplayer game Turn control between players Chat without GUI (Suffering) Real-time moving using...