python socket server multiple connections

It looks like you call encode('utf-8') in the server, and decode('utf-8') in the client. Print('Connection from', client_addr) Avoid transcoding between bytes and strings But you don't need to call any extra function, since the address of the peer is already stored in client_addr, so just write: That should have been client_sock.getpeername(). In your code you write: client_sock, client_addr = sock.accept() This looks very reasonable, but some improvements are possible: getsockname() returns the local side's address With StreamClient(('localhost', 1060)) as stream: Yield self._recvall(item_size).decode('utf-8') (item_size,) = HEADER_FORMAT.unpack(self._recvall(HEADER_FORMAT.size)) Raise EOFError('Socket closed during message transmission') Self.sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) Print('Client queue sizes:', server.get_qsizes()) With StreamServer(('localhost', 1060)) as server: Print('Connection from', client_sock.getsockname()) # Refuse connections once client limit reachedĬlient = _ClientHandler(client_sock, client_addr, self) Print('Listening at', sock.getsockname()) tsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) With socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock: '''Listen for incomming client connections.''' '''Close client socket and delete client thread.'''ĭel self._clients # Delete only client thread reference (garbage collection?) Print('Client', (), 'reached maximum qsize') '''Disconnect clients and remove client threads when leaving context.'''įor ident, client in self._ems(): '''Pop items from queue and sent to client.'''ĭef _exit_(self, exc_type, exc_value, traceback): It's my first time writing network code in Python (and in general), so I'm looking for ANY advice or suggestions.ĭef _init_(self, sock, address, server): To avoid that a buggy client brings down the server, I have a capped message queue for each client and the client gets disconnected once the queue reaches a defined limit. I send individual variable-length items by prefixing them with their length and then read this number of bytes of on the client side. Further, it allows me to develop a new module and connect it once it is ready for deployment, without interfering with my production modules. one client might write items to a DB, while another calculates some metrics etc.). This allows me to process data in different ways simultaneously (e.g. With this setup, I can start my server ONCE and then forward the data to any number of connecting clients. I was in need for such an architecture since I want to retrieve and process data from a public streaming endpoint, however the company limits the number of active connections to one per user. I wrote a server-client application in Python where the server sends a never-ending stream of messages to connecting clients.

Python socket server multiple connections