Timeline for Inter-language Communication
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2017 at 0:46 | vote | accept | namarino41 | ||
| Jun 28, 2017 at 22:53 | answer | added | RibaldEddie | timeline score: 2 | |
| Jun 28, 2017 at 22:26 | answer | added | John Wu | timeline score: 2 | |
| Jun 28, 2017 at 22:02 | comment | added | amon | Quite related, but not a clear duplicate: local communications between two apps | |
| Jun 28, 2017 at 21:19 | comment | added | Robert Harvey | Yes, that would follow. Someone mentioned JSON below; the nice thing about JSON and XML are that those rules are standardized and well-understood, and you can get libraries that read and write those data formats in almost any programming language. That's not the entire protocol, of course; you still need some transport mechanism like TCP/IP or named pipes to move that data from one process to another. | |
| Jun 28, 2017 at 21:15 | comment | added | namarino41 | Rules that define how a language stores certain data so that the other language knows how to retrieve that data. | |
| Jun 28, 2017 at 21:12 | comment | added | Robert Harvey | What kind of rules? | |
| Jun 28, 2017 at 21:02 | comment | added | namarino41 | @robert Understood. And that protocol is going to essentially establish the rules for how certain types of data is written and read correct? | |
| Jun 28, 2017 at 20:48 | comment | added | Robert Harvey | Which programming language you use doesn't matter. What does matter is that you have an inter-process communications protocol that both programming languages support (either in the language natively, or in libraries). | |
| Jun 28, 2017 at 20:34 | comment | added | Ben Cottrell | Firstly it depends what kind of pattern you need - e.g. Request/Response, RPC, direct notification, broadcast, multicast, update-polling, reliable-vs-unreliable.. Choose some kind of transport and/or storage mechanism; for example - Sockets, Pipes, Shared Memory, Message Queues, Message Brokers, Databases, FileSystem, NoSQL Stores, Key-Value (cache) stores, REST, SOAP.. In most cases you'll need to think about message/data format, in which case consider XML, JSON, Google Protobufs. There are many possible approaches; the first job is choosing the right tool(s) for your specific problem. | |
| Jun 28, 2017 at 19:45 | comment | added | gnat | yeah sure short introduction, four answers in 40 minutes. Wonder how many attempts at short introduction is going to be there in 4 hours... Where to start? | |
| Jun 28, 2017 at 19:42 | comment | added | scriptin | @gnat I don't think that a short introduction to different ways of communication b/w programs would take an entire book. | |
| Jun 28, 2017 at 19:38 | answer | added | amon | timeline score: 7 | |
| Jun 28, 2017 at 19:37 | review | Close votes | |||
| Jul 3, 2017 at 3:01 | |||||
| Jun 28, 2017 at 19:18 | comment | added | gnat | "Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much..." (help center) | |
| Jun 28, 2017 at 19:17 | answer | added | Basile Starynkevitch | timeline score: 1 | |
| Jun 28, 2017 at 19:17 | answer | added | Peter M | timeline score: 1 | |
| Jun 28, 2017 at 19:10 | answer | added | TheCatWhisperer | timeline score: 0 | |
| Jun 28, 2017 at 19:03 | history | asked | namarino41 | CC BY-SA 3.0 |