Timeline for Concurrent Web Crawler
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 12, 2020 at 23:45 | history | bounty ended | Ludisposed | ||
| Oct 12, 2020 at 23:45 | vote | accept | Ludisposed | ||
| Oct 10, 2020 at 10:55 | comment | added | hjpotter92 | The functionality seems to be fine. Gathering results from channels is something which seems to me to be a personal preference. You can also try to take help of the merge and parallel digestion examples on this blog post: blog.golang.org/pipelines @Ludisposed | |
| Oct 9, 2020 at 14:36 | comment | added | Ludisposed | I'm only starting with go myself, but you've raised some valid points! Do you have any thoughts about the concurrency pattern? As it was the reason that prompted the question. IMHO the pattern seems off, (waiting till all goroutines are done before firing off the next batch) | |
| Oct 6, 2020 at 10:25 | history | answered | hjpotter92 | CC BY-SA 4.0 |