Hello everyone,
I would like to build a very simple chat messenger to use to exchange messages with computers connected to my home network (LAN).
I don't want to run a server on any of them, but instead, i'd like to broadcast the message to the full range of IPs of my router and if another client is running, receive it.
Is that possible with LC?
Serverless (P2P) chat application for local network
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Serverless (P2P) chat application for local network
Last edited by liagason on Sun Apr 29, 2018 5:36 pm, edited 1 time in total.
Re: Serverless (P2P) chat application for local network
I'm by no means an expert on LiveCode or messaging, but I've been playing around with chat systems for a couple of weeks now.
Assuming you're not going to have colossal numbers of clients on the network I can maybe see a way to fudge it.
If you treat every client as also being a server, and have each one pass on every message to the next one... I don't have time to explore it but it may be an avenue to explore if no one more knowledgeable than me suggests anything!
Assuming you're not going to have colossal numbers of clients on the network I can maybe see a way to fudge it.
If you treat every client as also being a server, and have each one pass on every message to the next one... I don't have time to explore it but it may be an avenue to explore if no one more knowledgeable than me suggests anything!
Re: Serverless (P2P) chat application for local network
http://lessons.livecode.com/m/4071/l/12 ... ng-sockets
To expand on this, if you look at the code for a server, all it does is accept connections on a certain port.
If you have each client do this, and then any time a client connects, it looks for another client, the two could connect and either can work as the server.
Then when a third connects, it looks for the first one that works as the server, and connects to it. The server sends it the list of connected users. Then if the server disconnects, one of the other clients picks up the role.
To expand on this, if you look at the code for a server, all it does is accept connections on a certain port.
If you have each client do this, and then any time a client connects, it looks for another client, the two could connect and either can work as the server.
Then when a third connects, it looks for the first one that works as the server, and connects to it. The server sends it the list of connected users. Then if the server disconnects, one of the other clients picks up the role.