diff options
| author | Nathan Torkington <gnat@prometheus.frii.com> | 1997-04-03 08:34:15 +1200 |
|---|---|---|
| committer | Chip Salzenberg <chip@atlantic.net> | 1997-04-03 10:03:25 +1200 |
| commit | 4a6725af9146bd7faaa10aa5429ff009d393fd6d (patch) | |
| tree | a3ce04fc20ee3f1d40bff76887a2a86aeab52ddf /pod/perlipc.pod | |
| parent | 203c3eeca2516d7ec08a0618594a5440ce517675 (diff) | |
| download | perl-4a6725af9146bd7faaa10aa5429ff009d393fd6d.tar.gz | |
Pod style
Diffstat (limited to 'pod/perlipc.pod')
| -rw-r--r-- | pod/perlipc.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod index 7dc1c7a9b5..86dda59137 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -483,7 +483,7 @@ If you're not writing a server/client for an existing protocol like NNTP or SMTP, you should give some thought to how your server will know when the client has finished talking, and vice-versa. Most protocols are based on one-line messages and responses (so one party -knows the other has finished when a "\n" is received) or multiline +knows the other has finished when a "\n" is received) or multi-line messages and responses that end with a period on an empty line ("\n.\n" terminates a message/response). |