Minor typo/grammar fixes in doc/commvis & sqlaccess
This commit is contained in:
parent
1059c4792a
commit
ec64b3fa9d
2 changed files with 3 additions and 2 deletions
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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<queue_create()> will create a message queue (type
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue