<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Qt for a high performance server]]></title><description><![CDATA[<p dir="auto">Hi<br />
I am developing a Qt mobile application which connects to a server which does some heavy duty processing. I dont use HTTP but just send JSON objects back and forth using simple TCP. Now I used TCPServer and implemented a neat multithreaded application that acts as the server. Normally one would use PHP or Java servelets to do this but I took this route and ended up with a "C++ server" which I think is very very rare. But enjoyed being able to use C++ and OOP instead of a scripting environment.</p>
<p dir="auto">My question is, is this a recommended route ? What if I have thousands of users connecting to the server per second, does the TCPServer, QNetworkAccessManager and QThread infrastructure scale up and handle this load?  Or does it end up similar to a standard web server and its limitations (if well written using threadpools etc) ?</p>
<p dir="auto">Thanks!<br />
Sanjit</p>
]]></description><link>https://forum.qt.io/topic/60403/qt-for-a-high-performance-server</link><generator>RSS for Node</generator><lastBuildDate>Wed, 07 Oct 2026 16:10:56 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/60403.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 06 Nov 2015 08:19:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Qt for a high performance server on Sat, 07 Nov 2015 22:34:04 GMT]]></title><description><![CDATA[<p dir="auto">Hi and welcome to devnet,</p>
<p dir="auto">The only answer I see is: benchmark. You have to test your server under heavy load to see how well it's doing.</p>
]]></description><link>https://forum.qt.io/post/297105</link><guid isPermaLink="true">https://forum.qt.io/post/297105</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Sat, 07 Nov 2015 22:34:04 GMT</pubDate></item></channel></rss>