Mostly I to do IP communication between forms started in their own process.
This is where CALL FORM will enhance building solutions a lot. Until now, it is a mess. Form: "someone called". Programmer: "what did he say?" Form: "don't know" Programmer: "but you know who called? Form: "no" Programmer: "ok, what should we do now?" Form: "should I cancel?" Programmer: "or maybe accept?" Form: "I think we should redraw and reload everything" Programmer: "we could ask <>God" Form: "<>God is empty" Programmer: "how could that happen?" Form: "the process Erazer did probably clear it" Programmer: "should I kill Erazer?" Form: "I would not do that" Programmer: "why?" Form: "he created <>God" Programmer: "this is a nightmare" Form: "how do we get out of this mess?" Programmer: "I will ask <>Luzfer" Form: "good idea!" Programmer: "<>Luzfer, what should we do?" <>Luzfer: "accept" -----Ursprüngliche Nachricht----- Von: 4D_Tech [mailto:[email protected]] Im Auftrag von David Adams Gesendet: Freitag, 3. Februar 2017 08:08 An: 4D iNug Technical <[email protected]> Betreff: What are people using inter-process communications for now? But I'm curious - what are other people using inter-process communications for now? I'm more interested in the problems your solving than the communications architecture, but any answer is fine. I've used message queues and IP communications largely for: ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
