Difference between revisions of "Configuration File"
From DocDataFlow
(→Configuration File) |
|||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Crawler's personalities are often configured by means of configuration files. | |
| − | + | There is no hard rule that dictates what format these configuration files should use. They could be text files, [[INI file|''INI files'']], XML-based files,... | |
| − | + | ||
| − | There is no hard rule that dictates | + | |
Because [[INI file|''INI files'']] are easy to understand for end-users, most of the pre-made personalities use INI-based configuration files. | Because [[INI file|''INI files'']] are easy to understand for end-users, most of the pre-made personalities use INI-based configuration files. | ||
| − | For more popular personalities, GUI-driven configuration tools might be provided, but in many cases, the GUI-development | + | For more popular personalities, GUI-driven configuration tools might be provided, but in many cases, the GUI-development will lag behind on the functionality, in which case the next easiest method to (re)configure a Crawler personality is to edit one or more configuration files. |
Latest revision as of 00:22, 28 December 2013
Crawler's personalities are often configured by means of configuration files.
There is no hard rule that dictates what format these configuration files should use. They could be text files, INI files, XML-based files,...
Because INI files are easy to understand for end-users, most of the pre-made personalities use INI-based configuration files.
For more popular personalities, GUI-driven configuration tools might be provided, but in many cases, the GUI-development will lag behind on the functionality, in which case the next easiest method to (re)configure a Crawler personality is to edit one or more configuration files.
