Best approach to manage subdomains dynamically in a Qt-based mobile app

[ellen]

Hi everyone,

I'm currently working on a Qt-based mobile application that needs to handle multiple subdomains dynamically based on user preferences. The app fetches data from different subdomains of our main domain, e.g., user1.example.com, user2.example.com, etc.

Currently, I'm using Q Network Access Manager to make API calls, but I'm wondering if there's a more efficient way to dynamically switch subdomains without affecting the app's performance. Has anyone dealt with a similar scenario?

Would appreciate any insights or recommendations on how to structure the API requests efficiently and whether implementing a caching layer within the app makes sense.

Thanks in advance!

[jsulm]

@ellen Not sure what the problem is. The user selects a domain and your app uses that domain to communicate via QNetwork AccessManager.

[GILOKILO]

I already had a similar case with Qt and QNetworkAccessManager. To manage the subdomains dynamically, I used a QNetworkRequest with a URL configured on the fly, and it works well without any noticeable impact on performance. Adding a cache layer (e.g. QNetworkDiskCache) can also improve efficiency if the data does not change too often.

[helpemailtales]

@ellen Hey! Using QNetworkAccessManager is a solid choice, and switching subdomains dynamically is pretty straightforward — you can just update the request URL as needed.

For performance, adding a caching layer (like QNetworkDiskCache) can help reduce redundant requests and speed things up. Also, if the subdomain list doesn’t change often, you might preload some data in the background.

Another option is to manage connections with separate QNetworkAccessManager instances if you need parallel requests to different subdomains.

What kind of data are you fetching? That might help fine-tune the approach!

[GrecKo]

Using QNetworkRequestFactory and changing its baseUrl in once place might help.