|
Check-in Number:
|
1047 | |
| Date: |
2001-Oct-01 18:26:14 (local)
2001-Oct-01 16:26:14 (UTC) |
| User: | ms |
| Branch: | |
| Comment: |
Fixed incorrect comments. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/l2/l2_ch_pipe.c 1.21 -> 1.22
--- l2_ch_pipe.c 2001/10/01 16:14:10 1.21
+++ l2_ch_pipe.c 2001/10/01 16:26:14 1.22
@@ -71,11 +71,21 @@
}
/*
- * A channel is the central object for a logging stream. It is
- * implemented by a framework (the code implemented here) which provides
- * the channel API and which is equal for all channels and a particular
- * handler which implements the characteristics specific to a particular
- * channel class. The lifecycle of a channel is illustrated in the
+ * The lifecycle of the command executed by the pipe channel handler
+ * depends on the runtime option selected during configuration. The
+ * option 'reliable' describes subsequent behavior which rebuilds an
+ * (un)intentionally severed child-controlled pipe. In this case, when
+ * the pipe handler encounters a failed write operation, it will attempt
+ * the reconnection a user-defined number of times until failure is assumed.
+ *
+ * The option 'oneshot' describes subsequent behavior which also rebuilds
+ * such a severed pipe. The difference is that the pipe handler will not
+ * spawn the child process until writing actually occurs. It will also
+ * terminate the child process after writing is finished, independant of
+ * whether the write operation succeeded or failed after the user-specified
+ * number of retries.
+ *
+ * The lifecycle of a pipe command process is illustrated in the
* following figure:
*
* -----BEGIN EMBEDDED OBJECT-----
|
|
