Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-20 Thread Giuseppe D'Angelo
On 20 January 2013 17:29, Scott Aron Bloom scott.bl...@onshorecs.com wrote: Honestly, if qNAM had the ability to set the timeout, I would have no problem with a blocking call.. Start a QTimer and abort the QNetworkReply if it fires before finished(), and viceversa. Cheers, -- Giuseppe

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-19 Thread Mandeep Sandhu
Blocking at the end, is ok... Blocking while the application is running is not. Yes, I want my cake and to eat is as well :) I essentially want to kick off the request at the beginning of the run, then let the request run its course in the backround. If the main application (no event

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-18 Thread Mandeep Sandhu
, January 17, 2013 5:27 PM To: interest@qt-project.org Subject: Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application On sexta-feira, 18 de janeiro de 2013 00.59.13, Scott Aron Bloom wrote: I have a command line application, with no event loop. We can stop here

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-18 Thread R. Reucher
On Friday 18 January 2013 10:02:24 Mandeep Sandhu wrote: Just curious here, but why don't you want to run the event loop in the main thread but only run it in a different thread? Probably because the environment it's going to be used in already utilizes its own event loop... I had a similar

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-18 Thread Scott Aron Bloom
] QNetworkAccessManager in a command line, non-eventloop application On sexta-feira, 18 de janeiro de 2013 00.59.13, Scott Aron Bloom wrote: I have a command line application, with no event loop. We can stop here. QNetworkAccessManager requires an event loop. But if you're going to block anyway

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-18 Thread Scott Aron Bloom
On sexta-feira, 18 de janeiro de 2013 01.49.35, Scott Aron Bloom wrote: I don't want to block Yet you're describing exactly a blocking situation: I would like a background thread and have the request run in there, using the QThreads event loop. The background thread runs an event loop,

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-18 Thread Thiago Macieira
On sexta-feira, 18 de janeiro de 2013 17.08.46, Scott Aron Bloom wrote: On sexta-feira, 18 de janeiro de 2013 01.49.35, Scott Aron Bloom wrote: I don't want to block Yet you're describing exactly a blocking situation: I would like a background thread and have the request run in there,

[Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-17 Thread Scott Aron Bloom
I have a command line application, with no event loop. I also have a function where I need the tool to send a HTML request out, and not care about the result.. There is 1 and only 1 QNAM. I know what the issue is, there is NO event loop, what I would like to do is have a QThread (or a

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-17 Thread Thiago Macieira
On sexta-feira, 18 de janeiro de 2013 00.59.13, Scott Aron Bloom wrote: I have a command line application, with no event loop. We can stop here. QNetworkAccessManager requires an event loop. But if you're going to block anyway in order to do work, you can use QEventLoop to start the event loop

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

2013-01-17 Thread Scott Aron Bloom
] QNetworkAccessManager in a command line, non-eventloop application On sexta-feira, 18 de janeiro de 2013 00.59.13, Scott Aron Bloom wrote: I have a command line application, with no event loop. We can stop here. QNetworkAccessManager requires an event loop. But if you're going to block anyway in order to do