David, This may be a little off your interest but I'm using a server process to collect data from across the database for building real time graphs for users. The collection involves a lot of searching and aggregating so it would be incredibly inefficient to do for each machine. Background process on server runs periodically and populates some IP arrays with the data (object array in v15).
Client machines run a method which executes on server and copies the data to local arrays on their machines via pointers. Very fast. Particularly good for us since we operate over a WAN. And low footprint - the clients never populate the IP vars. This trick of using EOS to allow any client machine to grab IP vars from the server is pretty cool. I think someone built a chat module using the approach some time ago. On Thu, Feb 2, 2017 at 11:08 PM, David Adams <[email protected]> wrote: > > 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. -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 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] **********************************************************************
