Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: multithread client socket Date: Wed, 2 Dec 2015 14:38:37 -0000 (UTC) Organization: A noiseless patient Spider Lines: 22 Message-ID: References: <75df5111-41b9-4833-8497-69104f011d14@googlegroups.com> <69d9875d-3428-4f7a-8ddf-93a983091dcd@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 2 Dec 2015 14:38:37 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="e5160e2be48f1ea550cf61512446f525"; logging-data="8917"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18GCf6ywJb6LnLky5N3jn+AY2hHIeLStUw=" User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Cancel-Lock: sha1:UrZizzbugprMi738n0mQsSGjRnI= Xref: csiph.com comp.lang.java.programmer:33269 On Tue, 01 Dec 2015 23:04:11 -0800, Philipp Kraus wrote: > I don't use a server socket, it is only a client socket > I should hope not! Server sockets are server's tool for being notified about incoming connections. Used by me as an illustration of how typical server logic works and why its a bad idea for a server to close connections opened by the client. When you open a Socket you pass it the address and port number of the server's ServerSocket. This accepts the connection and immediately spawns a Socket instance which gets passed to the server code that reads and responds to the client's request(s). Meanwhile the ServerSocket goes on listening for more incoming requests. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |