Revision: 51822
http://brlcad.svn.sourceforge.net/brlcad/?rev=51822&view=rev
Author: carlmoore
Date: 2012-08-08 15:54:52 +0000 (Wed, 08 Aug 2012)
Log Message:
-----------
fix spellings
Modified Paths:
--------------
brlcad/trunk/doc/pkg.tr
Modified: brlcad/trunk/doc/pkg.tr
===================================================================
--- brlcad/trunk/doc/pkg.tr 2012-08-08 15:52:04 UTC (rev 51821)
+++ brlcad/trunk/doc/pkg.tr 2012-08-08 15:54:52 UTC (rev 51822)
@@ -218,7 +218,7 @@
byte stream buffer. If the current message is less
than MAXQLEN (currently 512) bytes in length, and space
remains for it, it will be appended onto the end of this
- buffer. Otherwise the buffer is implicity flushed by
+ buffer. Otherwise the buffer is implicitly flushed by
sending this message via PKG_SEND.
PKG_FLUSH - Flush the stream buffer out on the connection
@@ -280,7 +280,7 @@
The user may specify handlers for one or more message types.
When these routines are called they are passed a pointer
to the connection and a pointer to a buffer that contains
- the message. The user message handler routine is resonsible
+ the message. The user message handler routine is responsible
for freeing the message buffer after processing it. If there
is no message handler for that message type the message is
discarded and the buffered freed. The switch routine uses
@@ -290,7 +290,7 @@
The pkg_switch list which is passed to some of the above
functions is a NULL terminated array of structures containing
the message type, a pointer to an function which handles
- messages of that type, and a descriptive string. A seperate
+ messages of that type, and a descriptive string. A separate
pkg_switch array is kept for each connection so that several
entirely different PKG conversations can be carried out by a
single application at the same time.
@@ -357,9 +357,9 @@
It is not anticipated that full asynchronous I/O implementation will
work particularly well across domain boundaries, but all other forms
of message transfer should work quite well. As already noted, buffered
-stream I/O may be prefectly satisfactory for many applications where
+stream I/O may be perfectly satisfactory for many applications where
full interaction is not required. Where applicable, this mode of
-interface is to be prefered over full asynchronous I/O. Further
+interface is to be preferred over full asynchronous I/O. Further
development of this interface layer on other protocol families is
possible, perhaps even on low level networks like BITNET and certainly
on connection oriented X.25 or OSI networks.
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BRL-CAD Source Commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-commits
