Mercurial > noffle
comparison src/client.c @ 331:ff7a2dc6023e noffle
[svn] * src/client.c,src/group.c: Reunite forbidden group comment with code, and
revise forbidden rules to allow single component names except for some
specific ones.
| author | bears |
|---|---|
| date | Wed, 26 Feb 2003 11:30:41 +0000 |
| parents | 1aa690671cd7 |
| children | 278a03a392b1 |
comparison
equal
deleted
inserted
replaced
| 330:56c3a43af1d5 | 331:ff7a2dc6023e |
|---|---|
| 1 /* | 1 /* |
| 2 client.c | 2 client.c |
| 3 | 3 |
| 4 $Id: client.c 430 2003-02-10 18:28:30Z bears $ | 4 $Id: client.c 466 2003-02-26 11:30:41Z bears $ |
| 5 */ | 5 */ |
| 6 | 6 |
| 7 #if HAVE_CONFIG_H | 7 #if HAVE_CONFIG_H |
| 8 #include <config.h> | 8 #include <config.h> |
| 9 #endif | 9 #endif |
| 32 #include "pseudo.h" | 32 #include "pseudo.h" |
| 33 #include "request.h" | 33 #include "request.h" |
| 34 #include "util.h" | 34 #include "util.h" |
| 35 #include "wildmat.h" | 35 #include "wildmat.h" |
| 36 #include "portable.h" | 36 #include "portable.h" |
| 37 | |
| 38 /* | |
| 39 Some newsgroups names are reserved for server-specific or server | |
| 40 pseudo groups. We don't want to fetch them. For example, INN | |
| 41 keeps all its control messages in a 'control' hierarchy, and | |
| 42 used the "to." hierarchy for dark and mysterious purposes I think | |
| 43 are to do with newsfeeds. The recommended restrictions are documented | |
| 44 in C.Lindsay, "News Article Format", <draft-ietf-usefor-article-03.txt>. | |
| 45 */ | |
| 46 | 37 |
| 47 struct | 38 struct |
| 48 { | 39 { |
| 49 FILE* in; /* Receiving socket from server */ | 40 FILE* in; /* Receiving socket from server */ |
| 50 FILE* out; /* Sending socket to server */ | 41 FILE* out; /* Sending socket to server */ |
