Re: About separate processes and threads

On Tue, Oct 16, 2018 at 4:07 PM vitalije wrote: I don't have much time to write right now, but here is a list of (IMHO) > essential facts one should keep in mind when dealing with concurrency: > A great summary. Many thanks for this. I've bookmarked this reply and will study the features you

Re: About separate processes and threads

> > I am enjoying this. The real reason I wrote the original post was to get > some help in understanding processes, thread and servers. > > I'll interrupt my study to ask this rhetorical question. Why do I think this > hilarious cartoon applies to Leo's >

Re: About separate processes and threads

Their was a book on Ada I bought a few decades ago that dealt with locks and other interprocess stuff. The author explained things by diagrams that had button, (push and pull), hatches and other things that illustrated how the various concepts worked in a graphical mechanistic fashion,

Re: About separate processes and threads

On Tue, Oct 16, 2018 at 8:55 AM Terry Brown wrote: > On Tue, 16 Oct 2018 04:36:31 -0700 (PDT) > "Edward K. Ream" wrote: > > > The original Dreaming Big Dreams thread suggested reorganizing Leo > > into more separable pieces, perhaps using a client/server > > architecture or other forms of

Re: About separate processes and threads

On Tue, 16 Oct 2018 04:36:31 -0700 (PDT) "Edward K. Ream" wrote: > The original Dreaming Big Dreams thread suggested reorganizing Leo > into more separable pieces, perhaps using a client/server > architecture or other forms of interprocess communication (IPC). Here's a presentation I just gave:

About separate processes and threads

The original Dreaming Big Dreams thread suggested reorganizing Leo into more separable pieces, perhaps using a client/server architecture or other forms of interprocess communication (IPC). Here I'd like to present what little I know about IPC, servers and threads. The purpose is continue the