Timeline for Word for application that is both sender and receiver
Current License: CC BY-SA 3.0
32 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 17, 2020 at 3:54 | comment | added | Albert Renshaw |
Someone else asked this a few years later and a great answer was posted, Correspondent (not to be confused with Corespondent ) -- english.stackexchange.com/q/369828/33559
|
|
Nov 2, 2011 at 10:59 | comment | added | Lee Kowalkowski | How about naming it based on what it's for rather than how it does it? E.g. mirror, backup, share, cache. | |
Nov 2, 2011 at 0:41 | history | protected | RegDwigнt | ||
Nov 1, 2011 at 23:33 | answer | added | Bill | timeline score: 0 | |
Nov 1, 2011 at 20:40 | answer | added | weir | timeline score: 1 | |
Nov 1, 2011 at 19:53 | history | edited | user2683 | CC BY-SA 3.0 |
deleted 6 characters in body; edited title
|
Nov 1, 2011 at 19:33 | answer | added | Chris Cudmore | timeline score: 0 | |
Nov 1, 2011 at 18:51 | history | edited | Daniel | CC BY-SA 3.0 |
edited body
|
Nov 1, 2011 at 18:46 | comment | added | pixelbobby | I'm a Sr. Software Engineer in the IT field, and I will agree with @MarkBooth on this one. However, in a network structure, you may refer to something like this simply as a "node" by default. But I think "peer" is suffice for application development whereas "node" may be more of a networking term. | |
Nov 1, 2011 at 18:05 | answer | added | David Schwartz | timeline score: 4 | |
Nov 1, 2011 at 17:44 | answer | added | Christoffer Hammarström | timeline score: 3 | |
Nov 1, 2011 at 17:41 | comment | added | psr | Coin your own. Call it a chatterbox. | |
Nov 1, 2011 at 17:19 | history | tweeted | twitter.com/#!/StackEnglish/status/131420056419696641 | ||
Nov 1, 2011 at 16:58 | answer | added | Edson Medina | timeline score: 2 | |
Nov 1, 2011 at 16:56 | answer | added | stoolburger | timeline score: 3 | |
Nov 1, 2011 at 15:45 | answer | added | jftuga | timeline score: 1 | |
Nov 1, 2011 at 14:57 | answer | added | Tyrone Skogstrom | timeline score: 0 | |
Nov 1, 2011 at 14:41 | comment | added | Mark Booth | Most network applications both send and receive, that is the nature of communication. In a client/server system the client usually makes requests and the server services them, replying with requested data or replying that data was or wasn't received. Since you are creating a peer application, each instance of your application is a peer so could be named as such, e.g. MyApplicationPeer. | |
Nov 1, 2011 at 14:29 | comment | added | Fraser Orr | How about hermaphrodite? :-) | |
Nov 1, 2011 at 13:58 | answer | added | artifex | timeline score: -2 | |
Nov 1, 2011 at 13:48 | comment | added | LarsTech | .......Bipolar? | |
Nov 1, 2011 at 13:33 | answer | added | Phil | timeline score: 12 | |
Nov 1, 2011 at 13:31 | history | edited | Hugo | CC BY-SA 3.0 |
Added OP's clarifying comment to the question
|
Nov 1, 2011 at 13:26 | answer | added | Ergwun | timeline score: 32 | |
Nov 1, 2011 at 13:23 | answer | added | bakoyaro | timeline score: 0 | |
Nov 1, 2011 at 9:46 | history | edited | Ed Guiness |
edited tags
|
|
Nov 1, 2011 at 9:18 | answer | added | Hugo | timeline score: 3 | |
Nov 1, 2011 at 8:25 | answer | added | Darren | timeline score: 40 | |
Nov 1, 2011 at 7:53 | comment | added | Akbar | This is a peer application running on two different machines, sending/receiving data to-and-fro with its peer. | |
Nov 1, 2011 at 7:15 | comment | added | Codie CodeMonkey | Can you give some more details? There might be a more precise word that we can suggest if we know more about the role of this program. | |
Nov 1, 2011 at 6:38 | history | edited | Hugo | CC BY-SA 3.0 |
deleted 1 characters in body; edited title
|
Nov 1, 2011 at 6:28 | history | asked | Akbar | CC BY-SA 3.0 |