@raven-worx @artwaw As a result of my research, I came to this truth too. Still, I wanted to get answers from the authorities before finalizing my research completely. Thank you very much for your answers. Best regards Abbas Perçin

@Sprezzatura I think this looks better :) Your code as it stands presumably leaks QNetworkRequest *request = new QNetworkRequest(url); and QNetworkAccessManager *nam = new QNetworkAccessManager;. You could put these on the stack (no pointers, no new). And I think you're supposed to deleteLater() the QNetworkReply *reply = nam->post(*request, content);. You can get away without, but one day when you want examine your code for memory leaks with e.g. valgrind it will be better.

@Ahmed-Yarub-Hani-Al-Nuaimi Oh ok I see, thanks for your time !

@Saman19 You may want to check out Cutelyst if you want to support the HTTP protocol. If you do not need to rely on HTTP, but just want to receive JSON (or any custom protocol), take a look at QTcpServer examples.

Hi, AFAIK, no. IIRC KDevelop has some stuff already implemented for Docker, but not Qt Creator.

@raven-worx Yes, this is the code. I also did separate new code QNAM()->PUT(request,QFile*) & QNAM()->POST(request,QFile*) on my QT 5.4.1 setup. Everytime after executing the request application memory goes on increasing till it is equivalent to given file size(here I used 1GB file & memory increased by 1GB).

The server is not returning anything useful in the HTTP headers (I wouldn't expect it to): ~/tmp$ wget -S 'http://u801.wapkafile.com//g03/video/1253022/7940/c8f9a32ef15648bfa6f693102de27835/DARNA-ZAROORI-HAI-3(Movies7.In).avi?md5=TU7ibYa85byjzJyJcH_LXQ&expires=1458916610' --2016-07-27 18:21:15-- http://u801.wapkafile.com//g03/video/1253022/7940/c8f9a32ef15648bfa6f693102de27835/DARNA-ZAROORI-HAI-3(Movies7.In).avi?md5=TU7ibYa85byjzJyJcH_LXQ&expires=1458916610 Resolving u801.wapkafile.com (u801.wapkafile.com)... 8.37.229.38 Connecting to u801.wapkafile.com (u801.wapkafile.com)|8.37.229.38|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Server: nginx Date: Wed, 27 Jul 2016 08:21:15 GMT Content-Type: video/x-msvideo Content-Length: 65707724 Connection: keep-alive Last-Modified: Wed, 31 Dec 2014 06:15:08 GMT Content-Disposition: attachment; filename="DARNA-ZAROORI-HAI-3(Movies7.In).avi" Accept-Ranges: bytes Expires: Wed, 03 Aug 2016 06:34:10 GMT Cache-Control: max-age=604800 Cache-Control: s-maxage=604800,max-age=604800 Age: 6425 X-Cache: HIT TCP_MEM_HIT dirn:0:1402323922 X-Swift-SaveTime: Wed, 27 Jul 2016 06:34:10 GMT X-Swift-CacheTime: 604800 Via: 440d210b[0,206-0,H] Length: 65707724 (63M) [video/x-msvideo] Saving to: 'DARNA-ZAROORI-HAI-3(Movies7.In).avi?md5=TU7ibYa85byjzJyJcH_LXQ&expires=1458916610.1’ So Download Manager must be getting the info from the metadata at the start of the file. For example, I only downloaded the first 70KB of the file, and: ~/tmp$ file DARNA-ZAROORI-HAI-3\(Movies7.In\).avi\?md5=TU7ibYa85byjzJyJcH_LXQ\&expires=1458916610 DARNA-ZAROORI-HAI-3(Movies7.In).avi?md5=TU7ibYa85byjzJyJcH_LXQ&expires=1458916610: RIFF (little-endian) data, AVI, 640 x 360, ~30 fps, video: H.264 X.264 or H.264, audio: MPEG-1 Layer 3 (stereo, 22050 Hz) So the info is there at the start. I expect you'll want to use a library to parse it out. I'm not sure if Qt has such functionality built-in. Perhaps have a look through the Qt Multimedia docs. Cheers.

@djee In My Way connectToHost To Http Server Not Working, So I Call QSslConfiguration::defaultConfiguration(); Instead.

Hi, Why are you creating your request on the heap rather than stack ? Also, you never delete the request so you might be covering one with another and you have a memory leak.

@SujaMM I'm trying to do exactly what you're attempting to do. But in my case, all my code works except for how I create my signature (the response from aws server says that their signature is different than mine, therefore my request won't go through). If its possible, could you show me how you're creating your signature? If I can create my signature correctly and it goes through, I can post the source code for you to pick apart and choose what you want to use. I just keep failing on this signature creation business >.<

@TioRoy Obrigado pela resposta. Acabei fazendo com a biblioteca ffmpeg, pois consegui buscar os dados e jogar pra fora em multicast mas fica travando, estou errando em algum lugar.

@mcosta i am able to view the page inside the browser tho, why can't Qt read it then?

Hi and welcome to devnet, For the bluetooth side Qt 5.5 is more likely what you are looking for. As for developing on both mobile platform, currently it's indeed mandatory to have an OS X system. Virtualbox seems to only support Mac OS X Server (Leopard, Snow Leopard). At least it's what they lists. Also note that to be able to test your application on your iPhone/Pad etc. as well as submit it to the App Store, you need to enroll in the iOS developer program Hope it helps

You can try using more QNAM bur in the end, creating many connection won't make it faster since you'll have a bottleneck with your connection's speed

This must be the part that you want void MyServer::StartServer() { thisIp = 2346; if(!this->listen(QHostAddress::Any, thisIp)) { qDebug() << "Could not start server."; qDebug() << errorString(); } else { qDebug() << "Listening at" << thisIp; } } and here is the original. tutorial.

Maybe my HTTP server library helps you: http://stefanfrings.de/qtwebapp/index-en.html It's multi-threaded.