One needs to send 1 mln HTTP requests concurrently, in batches, and read the responses. No more than 100 requests at a time.

Which way will it be better, recommended, idiomatic?

  • Send 100 ones, wait for them to finish, send another 100, wait for them to finish… and so on

  • Send 100 ones. As a a request among the 100 finishes, add a new one into the pool. “Done - add a new one. Done - add a new one”. As a stream.

    • Gamma@beehaw.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      9 months ago

      They did the same a few days ago and deleted the post before reposting

      • cuenca@lemm.ee
        cake
        OP
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        9 months ago

        Yes, they did. The fucking commentators here are really fucking.

    • cuenca@lemm.ee
      cake
      OP
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Kmz, I’m JUST trying to GET help but they’re being a bunch of cocks?

      • xor@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        9 months ago

        They’re trying to work out what problem you’re trying to solve, so they can give you actually useful advice for your - frankly - very vague question

        “What are you trying to achieve” is a perfectly reasonable question to ask about a deeply under-specified problem

        Edit: here’s my theory:

        This is a homework or interview question you’ve been asked, that depends on specific context that you haven’t included (because you don’t know what context is even relevant)

        You don’t want to admit that’s why you’re asking, because you know that defeats the point of you being asked in the first place.

        Hence, you’re being absurdly hostile to someone trying to help, because you can’t answer their question without admitting you’re trying to cheat