summaryrefslogtreecommitdiff
path: root/docs/tutorials/015/page16.html
diff options
context:
space:
mode:
authorjcej <jcej@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-10-20 02:05:16 +0000
committerjcej <jcej@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-10-20 02:05:16 +0000
commit2ae14b2b85ad813a269e8a5529aa76cf984fa8a5 (patch)
treebafa76246f16ad4d1b7d54baccaf335a7f44d7c2 /docs/tutorials/015/page16.html
parentfbacb099c89a0c51a37d632322e1f8952937eda8 (diff)
downloadATCD-2ae14b2b85ad813a269e8a5529aa76cf984fa8a5.tar.gz
*** empty log message ***
Diffstat (limited to 'docs/tutorials/015/page16.html')
-rw-r--r--docs/tutorials/015/page16.html16
1 files changed, 12 insertions, 4 deletions
diff --git a/docs/tutorials/015/page16.html b/docs/tutorials/015/page16.html
index 75ca714d7dd..0ff4b76ec8a 100644
--- a/docs/tutorials/015/page16.html
+++ b/docs/tutorials/015/page16.html
@@ -12,10 +12,18 @@
<P>
<HR WIDTH="100%">
-The Recv implementation is nearly as simple as Xmit. There's
-opportunity for error when we get the message size and we have to
-manage the lifetime of the tickler but other than that it's pretty
-basic stuff.
+Recv is the sibling to Xmit. Again, they could be combined into a
+single object if you want.
+<P>
+An ACE_Stream is designed to handle downstream traffic very
+well. You put() data into it and it flows along towards the tail.
+However, there doesn't seem to be a way to put data in such that it
+will travel upstream. To get around that, I've added a get() method
+to Recv that will trigger a read on the socket. Recv will then put
+the data to the next upstream module and we're on our way. As noted
+earlier, that data will eventually show up either in the <i>reader</i>
+(if installed on the stream open()) or the stream head reader task's
+message queue.
<HR>
<PRE>