From ec64b3fa9d72d27192e32acc6d1db0e6152d80cd Mon Sep 17 00:00:00 2001 From: Yorhel Date: Sat, 17 Mar 2012 12:29:43 +0100 Subject: [PATCH] Minor typo/grammar fixes in doc/commvis & sqlaccess --- dat/doc-commvis | 2 +- dat/sqlaccess | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/dat/doc-commvis b/dat/doc-commvis index e8e6142..5638bff 100644 --- a/dat/doc-commvis +++ b/dat/doc-commvis @@ -349,7 +349,7 @@ integer and float is blurred. Making my vision of modularity and ease of use a reality requires that any session can easily communicate with an other session, even if they have a vastly different implementation. To do this, we need a protocol to connect -multiple processes together, whether they run on a local machine or on over a +multiple processes together, whether they run on a local machine or over a physical network. =item Coding the stuff diff --git a/dat/sqlaccess b/dat/sqlaccess index 11f5c2b..3ba0ab2 100644 --- a/dat/sqlaccess +++ b/dat/sqlaccess @@ -274,7 +274,8 @@ Message passing schemes and libraries are available for many programming languages and come in many different forms. For this article, I am going to assume that an asynchronous and unbounded FIFO queue is used to pass around messages, but most of the following discussion will apply to bounded queues as -well. I'll try to note the important differences between two where applicable. +well. I'll try to note the important differences between the two where +applicable. A very simple and naive implementation of a message passing solution is given below. Here I assume that C will create a message queue (type