PageRenderTime 51ms CodeModel.GetById 21ms RepoModel.GetById 1ms app.codeStats 0ms

/README.md

https://github.com/glenjamin/node-intro-challenge
Markdown | 63 lines | 43 code | 20 blank | 0 comment | 0 complexity | 8244bcb3e7b7de64987b8e95e1a3cf2d MD5 | raw file
    

  1. # NodeJS What, Why & How Challenge
    2. 

  2. 

  3. This short challenge introduces you to handling control flow while making
    4. 

  4. asynchronous HTTP requests to major search engines.
    5. 

  5. 

  6. Be careful which files you open, as all the solutions are already present
    7. 

  7. in this repository.
    8. 

  8. 

  9. ## 0. Setup
    10. 

  10. 

  11. The file `setup.js` contains a short bit of bootstrap which will time your
    12. 

  12. script and also provides the search URLs.
    13. 

  13. 

  14.     > node setup
    15. 

  15.     { google: 'http://google.com/search?q=',
    16. 

  16.       bing: 'http://www.bing.com/search?q=',
    17. 

  17.       yahoo: 'http://search.yahoo.com/search?p=',
    18. 

  18.       ask: 'http://www.ask.com/web?q=',
    19. 

  19.       duck: 'http://duckduckgo.com/?q=' }
    20. 

  20. 

  21. Start with `challenge.js`, which requires the URL list and takes the search
    22. 

  22. terms from the command line.
    23. 

  23. 

  24. Useful Links:
    25. 

  25. http://nodejs.org/docs/latest/api/http.html
    26. 

  26. http://nodejs.org/docs/latest/api/url.html
    27. 

  27. 

  28. ## 1. Parallel HTTP requests
    29. 

  29. 

  30. Use node's stdlib HTTP client to make a request to each of the search engines
    31. 

  31. and then print the first 100 characters of the response to the console.
    32. 

  32. 

  33. Solution: `challenge-parallel.js`
    34. 

  34. 

  35. ## 2. Serial HTTP requests
    36. 

  36. 

  37. To demonstrate the complexities of control flow with async, now modify your
    38. 

  38. previous solution to make the requests one-at-a-time.
    39. 

  39. 

  40. You can try and do this by hand, or use the async library.
    41. 

  41. 

  42. Solutions: `challenge-series.js` `challenge-series-async.js`
    43. 

  43. 

  44. ## 3. Parallel requests with summary
    45. 

  45. 

  46. Firing stuff off in parallel is easy enough, but knowing when asynchronous
    47. 

  47. tasks have completed is less so. Combine the results of all of the queries
    48. 

  48. into a single object keyed by engine name that contains the time taken to
    49. 

  49. process the request and the data.
    50. 

  50. 

  51.     {
    52. 

  52.         google: {time: 1.34, data: '<html>...' },
    53. 

  53.         yahoo: {time: 1.34, data: '<html>...' },
    54. 

  54.         bing: {time: 1.34, data: '<html>...' },
    55. 

  55.         ...
    56. 

  56.     }
    57. 

  57. 

  58. Again, you can try and do this by hand, or use the async library.
    59. 

  59. 

  60. Solutions: `challenge-summary.js` `challenge-summary-async.js`
    61. 

  61. 

  62. For bonus points pull the URL to the first result out of the data and include
    63. 

  63. that in the returned object.
    64. 

  64.