Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #13014
| From | glen herrmannsfeldt <gah@ugcs.caltech.edu> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Socket problem: read & write to same socket |
| Date | 2012-03-15 01:33 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <jjrgu1$260$1@speranza.aioe.org> (permalink) |
| References | (4 earlier) <4f5fc93f$0$295$14726298@news.sunsite.dk> <27729487.119.1331678296341.JavaMail.geo-discussion-forums@pbfz10> <4f5fce87$0$285$14726298@news.sunsite.dk> <jjolfv$qp$1@localhost.localdomain> <4f60c5d6$0$2499$da0feed9@news.zen.co.uk> |
RedGrittyBrick <RedGrittyBrick@spamweary.invalid> wrote: (snip) >> I've been thinking over the servers protocols I know. The only one I can >> think of where the process accepting the connection speaks first is SMTP, >> where the server that accepts the connection announces who it is before >> seeing what its peer has to say. Arguably, this is a slightly different >> case since SMTP is a peer-to-peer protocol rather than a client-server >> one. (snip) > TCP Based Daytime Service > One daytime service is defined as a connection based application on > TCP. A server listens for TCP connections on TCP port 13. Once a > connection is established the current date and time is sent out the > connection as a ascii character string (and any data received is > thrown away). The service closes the connection after sending the > quote. A TCP connection is bidirectional, with two separate data streams. TCP doesn't care which goes first. TCP uses a three-way handshake to open the connection, normally with no data in those packets, but I believe there can be. For UDP, the client has to go first, though there doesn't need to be any data in the request. A packet with data length zero can still be considered a request to the server. In some cases, a zero length reply could be considered an answer from the server. -- glen
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
Socket problem: read & write to same socket liyaohua.bupt@gmail.com - 2012-03-13 09:01 -0700
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 12:14 -0400
Re: Socket problem: read & write to same socket liyaohua.bupt@gmail.com - 2012-03-13 09:30 -0700
Re: Socket problem: read & write to same socket Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-03-13 10:30 -0700
Re: Socket problem: read & write to same socket Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-13 21:33 +0000
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 17:48 -0400
Re: Socket problem: read & write to same socket Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-13 22:03 +0000
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 18:25 -0400
Re: Socket problem: read & write to same socket Lew <lewbloch@gmail.com> - 2012-03-13 15:38 -0700
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 18:47 -0400
Re: Socket problem: read & write to same socket Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-13 23:33 +0000
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 19:35 -0400
Re: Socket problem: read & write to same socket Paul Cager <paul.cager@googlemail.com> - 2012-03-14 02:51 -0700
Re: Socket problem: read & write to same socket Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-15 00:45 +0000
Re: Socket problem: read & write to same socket Paul Cager <paul.cager@googlemail.com> - 2012-03-15 03:18 -0700
Re: Socket problem: read & write to same socket RedGrittyBrick <RedGrittyBrick@spamweary.invalid> - 2012-03-14 16:22 +0000
Re: Socket problem: read & write to same socket glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2012-03-15 01:33 +0000
Re: Socket problem: read & write to same socket Nigel Wade <nmw@le.ac.uk> - 2012-03-15 12:30 +0000
Re: Socket problem: read & write to same socket Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-13 23:00 +0000
Re: Socket problem: read & write to same socket Arne Vajhøj <arne@vajhoej.dk> - 2012-03-13 19:36 -0400
csiph-web