diff options
author | jcej <jcej@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-11-06 19:07:23 +0000 |
---|---|---|
committer | jcej <jcej@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-11-06 19:07:23 +0000 |
commit | 826eec3ff95468ce4b0b2178628db94949e930c5 (patch) | |
tree | f7c10f55c81f8abf737f4c506b9022862cf5ae79 /docs/tutorials/015/page16.html | |
parent | dfb3b7940183caf8489d1e763343cbbcc9664835 (diff) | |
download | ATCD-826eec3ff95468ce4b0b2178628db94949e930c5.tar.gz |
*** empty log message ***
Diffstat (limited to 'docs/tutorials/015/page16.html')
-rw-r--r-- | docs/tutorials/015/page16.html | 16 |
1 files changed, 4 insertions, 12 deletions
diff --git a/docs/tutorials/015/page16.html b/docs/tutorials/015/page16.html index 620950ad548..5f23b7e4e48 100644 --- a/docs/tutorials/015/page16.html +++ b/docs/tutorials/015/page16.html @@ -12,18 +12,10 @@ <P> <HR WIDTH="100%"> -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. +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. <HR> <PRE> |