| | 22 | |
| | 23 | What would be better about removing these uses of crawler? |
| | 24 | |
| | 25 | 1. The storage server would be more efficient in terms of accesses to its storage backend. This might turn out to matter when the storage backend is a cloud storage service and you pay per API call. (Or it might not, if the cost is cheap enough and the crawly way to do it is efficient enough.) |
| | 26 | |
| | 27 | 2. The crawling would be a quiescent process — something that finishes its job and then stops, and doesn't start again unless a user tells it to. I like this way of doing things. See wiki:FAQ#Q18_unobtrusive_software . |
| | 28 | |
| | 29 | 3. Some of these operations would be faster and better if done in the newly proposed way instead of by relying on a crawler. |
