QHttp and readyRead signals emit sequence

[balitong]

Thanks for the reply. I would try to do that.

However, my application would need to send to about 50 hosts at 10 post/sec each, I'm worrying about the performance of instantiating so many QHttp and freeing the memory.

What my application does is to read a list of data from database table and then send to separate hosts depending on an id. The host is only known at runtime. And this application would need to stay on for 24x7. Whenever there is data in the table, it would need to process and send to hosts.

Have anyone ran a load test on the performance of QHttp? Is there any other http libraries that you could recommend? I'm a newbie in the world of HTTP, so please forgive my ignorance. I would try to do a load test and ran the application for a few days with the new changes to see the performance though.

Thank you.

[wysota]

However, my application would need to send to about 50 hosts at 10 post/sec each, I'm worrying about the performance of instantiating so many QHttp and freeing the memory.

You can store once initialised objects and reuse them later instead of freeing them.

Don't you think sending 500 requests per second might be considered flooding the network?

Have anyone ran a load test on the performance of QHttp? Is there any other http libraries that you could recommend?

If any, then libcurl, but I doubt you'll get better performance. It processes requests sequentially too, afaik.

I'm a newbie in the world of HTTP, so please forgive my ignorance. I would try to do a load test and ran the application for a few days with the new changes to see the performance though.

I'm sure QHttp will suffice.

[balitong]

Hi,

I've tried your suggestion and it works fine. Thanks for the tip.

the 10 post/sec is for the total throughput, not 10 post/sec each as I've mentioned. This is an application to push user request coming in from another network to the client's http server.