On 05/09/2013 10:59 PM, Thiago Macieira wrote:
> On quinta-feira, 9 de maio de 2013 22.43.06, Justin Karneges wrote:
>>> Good. Then you can use QHostInfo, since it will use only 5 threads.
>>
>> I should have been more clear. I may not want 100 threads, but I also
>> don't want queries being blocke
On quinta-feira, 9 de maio de 2013 22.43.06, Justin Karneges wrote:
> > Good. Then you can use QHostInfo, since it will use only 5 threads.
>
> I should have been more clear. I may not want 100 threads, but I also
> don't want queries being blocked by others.
Our experience is that DNS servers o
On 05/09/2013 10:35 PM, Thiago Macieira wrote:
> On quinta-feira, 9 de maio de 2013 22.09.06, Justin Karneges wrote:
>> By that I meant I want the underlying implementation to be event-driven,
>> not simply the interface (QHostInfo is thread-backed). This is for a
>> server application that needs t
On quinta-feira, 9 de maio de 2013 22.09.06, Justin Karneges wrote:
> By that I meant I want the underlying implementation to be event-driven,
> not simply the interface (QHostInfo is thread-backed). This is for a
> server application that needs to make outbound HTTP requests in bulk as
> fast a
On 05/09/2013 08:57 PM, Thiago Macieira wrote:
> On quinta-feira, 9 de maio de 2013 19.36.45, Justin Karneges wrote:
>> Also, I'm not using QHostInfo, but rather my own resolver JDNS, because
>> I want the resolutions to be event-driven.
>
> What do you mean by that?
By that I meant I want the und
On quinta-feira, 9 de maio de 2013 19.36.45, Justin Karneges wrote:
> > QHostInfo has a short-lived cache, so it should work.
>
> Mmmm, if QHostInfo's cache behaves like any other DNS cache then I don't
> see this making a difference. Unless every cache hit causes the cache
> time to extend, there
On 05/09/2013 06:44 PM, Thiago Macieira wrote:
> On quinta-feira, 9 de maio de 2013 18.00.36, Justin Karneges wrote:
>>> I understand the feature would be useful in certain conditions, but I'm
>>> not
>>> sure yours is one of them. You can probably just easily override the
>>> QNetworkAccessManager
On quinta-feira, 9 de maio de 2013 18.00.36, Justin Karneges wrote:
> > I understand the feature would be useful in certain conditions, but I'm
> > not
> > sure yours is one of them. You can probably just easily override the
> > QNetworkAccessManager class and do the IP address verification. If it
On 05/09/2013 04:54 PM, Thiago Macieira wrote:
> On quinta-feira, 9 de maio de 2013 16.44.10, Justin Karneges wrote:
>> Hi people,
>>
>> I discussed this feature with Shane and went ahead and made a patch.
>>
>> The idea is to be able to explicitly specify a TCP host/port target for
>> an HTTP requ
On quinta-feira, 9 de maio de 2013 16.44.10, Justin Karneges wrote:
> Hi people,
>
> I discussed this feature with Shane and went ahead and made a patch.
>
> The idea is to be able to explicitly specify a TCP host/port target for
> an HTTP request, while leaving everything else alone. The HTTP Ho
Hi people,
I discussed this feature with Shane and went ahead and made a patch.
The idea is to be able to explicitly specify a TCP host/port target for
an HTTP request, while leaving everything else alone. The HTTP Host
header, TLS certificate validation, and TLS server name indication would
On Thu, May 9, 2013 at 7:55 AM, Matteo Brichese wrote:
> Hi, I'll register myself for bug-submitting soon (I'm behind a proxy right
> now).
>
> However, who is controlling the docs? There is a huge amount of missing info
> on the latest docs, I need to work with particles system and the docs is
On Thursday, 9 May 2013 16:45:23 CEST, Thiago Macieira wrote:
> The user's monospace font is called "Monospace". That is not a
> font name, it's
> an alias set by fontconfig, on systems that use fontconfig.
Ah, that's good to know. I obviously lack any fontconfig knowledge.
However, both KDE an
Hi, I'll register myself for bug-submitting soon (I'm behind a proxy right now).
However, who is controlling the docs? There is a huge amount of missing info on
the latest docs, I need to work with particles system and the docs is very
limited, it say that I need to use Affected element with onA
On quinta-feira, 9 de maio de 2013 14.09.36, Jan Kundrát wrote:
> Hi,
> it looks like Qt tries to respect the font settings of the underlying
> platform in many situations, but there's unfortunately no way (AFAIK) to
> get the user's preference for a monospace font. My use case is to fit well
> int
Hi,
it looks like Qt tries to respect the font settings of the underlying platform
in many situations, but there's unfortunately no way (AFAIK) to get the user's
preference for a monospace font. My use case is to fit well into the user's
desktop when showing and writing plaintext e-mails.
I've
On Thu, 9 May 2013, 魏越闽 wrote:
I have a crash issue when use QtQuick2 and QtQuick1 together:
https://bugreports.qt-project.org/browse/QTBUG-31064
Shall I try out this patch
https://codereview.qt-project.org/#change,55521,patchset=5 ?
Yes, please.
We'll hopefully have our own test results av
I have a crash issue when use QtQuick2 and QtQuick1 together:
https://bugreports.qt-project.org/browse/QTBUG-31064
Shall I try out this patch
https://codereview.qt-project.org/#change,55521,patchset=5 ?
--
Wei Yuemin
7FGame
-邮件原
On 9 May 2013 11:35, Matteo Brichese wrote:
> Hi everyone, I've found that the docs of the Emitter in QtQuick2 is wrong.
>
> http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick-particles2-emitter.html#burst-method-2
>
> The Burst method takes as first args the count and then X and Y, not as
> wr
Hi everyone, I've found that the docs of the Emitter in QtQuick2 is wrong.
http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick-particles2-emitter.html#burst-method-2
The Burst method takes as first args the count and then X and Y, not as written
in the docs.
I don't know how to make a bug repo
20 matches
Mail list logo
