[Checkins] SVN: zc.ngi/trunk/src/zc/ngi/README.txt Spelling
corrections.
Amos Latteier
amos at latteier.com
Sun Dec 10 01:36:15 EST 2006
Log message for revision 71512:
Spelling corrections.
Changed:
U zc.ngi/trunk/src/zc/ngi/README.txt
-=-
Modified: zc.ngi/trunk/src/zc/ngi/README.txt
===================================================================
--- zc.ngi/trunk/src/zc/ngi/README.txt 2006-12-09 15:19:11 UTC (rev 71511)
+++ zc.ngi/trunk/src/zc/ngi/README.txt 2006-12-10 06:36:13 UTC (rev 71512)
@@ -3,12 +3,12 @@
=========================
Network programs are typically difficult to test because they require
-setting up network connections, clientts, and servers. In addition,
+setting up network connections, clients, and servers. In addition,
application code gets mixed up with networking code.
The Network Gateway Interface (NGI) seeks to improve this situation by
separating application code from network code. This allows
-application and network code to be tested indepenndly and provides
+application and network code to be tested independently and provides
greater separation of concerns.
There are several interfaces defined by the NGI:
@@ -24,7 +24,7 @@
Create IConnection objects by making outgoing connections.
IClientConnectHandler
- Application callback that handles successful ot failed outgoing
+ Application callback that handles successful or failed outgoing
connections.
IListener
@@ -50,7 +50,7 @@
>>> import zc.ngi.testing
The testing module provides IConnection, IConnector, and IListener
-implentations. We'll use this below to illustrate how application code
+implementations. We'll use this below to illustrate how application code
is written.
Implementing Network Clients
@@ -58,7 +58,7 @@
Network clients make connections to and then use these connections to
communicate with servers. To do so, a client must be provided with an
-IConnector implemantation. How this happens is outside the scope of
+IConnector implantation. How this happens is outside the scope of
the NGI. An IConnector implementation could, for example, be provided
via the Zope component architecture, or via pkg_resources entry
points.
@@ -106,8 +106,8 @@
... print 'closed prematurely'
-The client impements the IClientConnectHandler and IInputHandler
-interfaces. More complex clients might implement these interfacs with
+The client implements the IClientConnectHandler and IInputHandler
+interfaces. More complex clients might implement these interfaces with
separate classes.
We'll instantiate our client using the testing connector:
@@ -120,12 +120,12 @@
failed connect: no such server
Our client simply prints a message (and gives up) if a connection
-fails. More complex applications might retry, waiting between attemps,
+fails. More complex applications might retry, waiting between attempts,
and so on.
The testing connector always fails unless given a test connection
ahead of time. We'll create a testing connection and register it so a
-connection can suceed:
+connection can succeed:
>>> connection = zc.ngi.testing.Connection()
>>> zc.ngi.testing.connectable(('localhost', 42), connection)
@@ -145,14 +145,14 @@
-> 'world\n'
-> 'how are you?\n'
-The test connection echoes data written to it, preceeded by "-> ".
+The test connection echoes data written to it, preceded by "-> ".
Active connections are true:
>>> bool(connection2)
True
-Test connections provide mehods generating test input and flow closing
+Test connections provide methods generating test input and flow closing
connections. We can use these to simulate network events. Let's
generate some input for our client:
@@ -335,7 +335,7 @@
===========
Test requests output data written to them. If output exceeds 50
-characters in length, it is wrapped by simply breakng the repr into
+characters in length, it is wrapped by simply breaking the repr into
50-characters parts:
>>> connection = zc.ngi.testing.Connection()
More information about the Checkins
mailing list