Does anyone know if the HTTPCaller sends multiple requests simultaneously, or if it's only one-at-a-time?
We're looking to make lots of calls to a web-API, and we don't want HTTPCaller to wait for a response to any given call before the next request is made. The web-API can handle multiple connections at once, and we would like HTTPCaller to do the same.
Can it do this? I can't see anything in the docs allowing setting the number of simultaneous connections.
+62Anecdotical evidence, from a few years ago, so treat with a grain of salt... The HTTPCaller sends one request per feature that comes in. So when I, by mistake, this this for a lot of features requesting HTML documents from a web server on a local network I kinda did a denial-of-service attack, so yes, I think it does send out the requests without waiting for a response on the previous one.
+18Anecdotical evidence, from a few years ago, so treat with a grain of salt... The HTTPCaller sends one request per feature that comes in. So when I, by mistake, this this for a lot of features requesting HTML documents from a web server on a local network I kinda did a denial-of-service attack, so yes, I think it does send out the requests without waiting for a response on the previous one.
Anecdotical evidence, from a few years ago, so treat with a grain of salt... The HTTPCaller sends one request per feature that comes in. So when I, by mistake, this this for a lot of features requesting HTML documents from a web server on a local network I kinda did a denial-of-service attack, so yes, I think it does send out the requests without waiting for a response on the previous one.
We've just done a few simple tests. And the answer is, it does not support multi threading. FME's HTTPCaller only has a single connection at any given time.
This idea has a potential solution:
https://knowledge.safe.com/content/idea/34725/httpcaller-to-support-parallel-processing.html
