|
While gopher returns text/plain documents for actual document requests. A request to a directory (such as /) will return specially encoded series of lines with each line being one directory entry or information line.
In the example above, the root directory at gopher.example.com knows about one DOCUMENT identified by 0 located at gopher://gopher.example.com:70/allabout.txt. It also knows about two other directory (which have their own listing files) at gopher://gopher.exmaple.com:70/stories and at gopher://gopher.ejemplo.co.es:70/. In addition there is a binary file, a link to an HTTP url, and several informative lines.
By passing each line of the directory listing into gopher_parsedir(), an associative array is formed containing a parsed out version of the data.
Beispiel 2. Using gopher_parsedir()
|
The values given by type are associated with the following constants.
Tabelle 1. Gopher Constants
Constant | Definition |
---|---|
GOPHER_DOCUMENT | Standard text/plain document. |
GOPHER_DIRECTORY | A resource containing a gopher formatted directory listing. |
GOPHER_BINHEX | A BinHex encoded binary file. |
GOPHER_DOSBINARY | A DOS formatted binary archive. |
GOPHER_UUENCODED | A UUEncoded file. |
GOPHER_BINARY | A generic binary file. |
GOPHER_INFO | An Informational entry |
GOPHER_HTTP | A reference to an HTTP resource. |
GOPHER_UNKNOWN | An unrecognized entry, the line will be returned in data. |
Zurück | Zum Anfang | Weiter |
Net_Gopher | Nach oben | Netzwerk Funktionen |
Hosting by: Hurra Communications GmbH
Generated: 2007-01-26 17:57:15