On quinta-feira, 12 de abril de 2018 15:44:54 PDT Sze Howe Koh wrote:
> Can QNAM re-use a TCP connection for multiple HTTP requests?
Yes. It's the default. You don't have to do anything to enable it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tec
On 13/04/18 10:22, Jason H wrote:
I thought so, but that makes me wonder even more given the recent discussion:
why does the maintenance tool not use them?
You have to keep a single QNetworkAccessManager and make each new
request from that. I haven't checked the code though.
I did check tha
I thought so, but that makes me wonder even more given the recent discussion:
why does the maintenance tool not use them?
> Sent: Thursday, April 12, 2018 at 8:11 PM
> From: "Hamish Moffatt"
> To: "Jason H"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Does QNetworkAccessManager suppo
On 13/04/18 10:03, Jason H wrote:
Http/s 1.1 with keep-alive should work too.
Make sure you're setting the right headers.
QNAM will do that for you automatically.
Hamish
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/
Http/s 1.1 with keep-alive should work too.
Make sure you're setting the right headers.
> Sent: Thursday, April 12, 2018 at 7:24 PM
> From: "Hamish Moffatt"
> To: interest@qt-project.org
> Subject: Re: [Interest] Does QNetworkAccessManager support HTTP persistent
> connections? (keep-alive)
>
>
On 13/04/18 08:44, Sze Howe Koh wrote:
Can QNAM re-use a TCP connection for multiple HTTP requests?
AFAICT, it always does, if you reuse the QNAM.
Even better if you can use HTTP/2 (needs Qt 5.10.1 or later to actually
work), where multiple logical connections can be made over the same TCP
c
Can QNAM re-use a TCP connection for multiple HTTP requests?
This feature would be very helpful for
https://bugreports.qt.io/browse/QTIFW-1130
Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listi
On Thursday, 12 April 2018 12:08:09 PDT René J.V. Bertin wrote:
> frame #7: 0x7fff97676cd1 libsystem_malloc.dylib`_malloc_fork_prepare
> + 49 frame #8: 0x7fff997fa161 libsystem_c.dylib`fork + 12
This is the "atfork" code, the one that causes all malloc locks to be dropped
in the child
On Thursday, 12 April 2018 11:32:43 PDT william.croc...@analog.com wrote:
> I view the most recent branch (5.11 in this case) as your bold move into new
> features and, as long as that branch is sub-versioned (5.11.x),
> the dust has not settled.
>
> It appeared that the dust had settled on 5.10 a
Hi,
A bit of a long shot, but since leveldb is used by QtWebEngine this might ring
a bell to someone here:
Below is a bit of backtrace of a Qt application (KDevelop) on Mac in which I've
started experimenting with using leveldb. Under certain conditions the entire
app freezes, and then I see t
It immediately failed one of my regression tests.
You should have known there was an issue because I here it has been fixed in
5.11
Of course there are problems. Do you want us to delete every old release
because we've fixed bugs? We already have fixes for bugs post 5.9.5, which was
released
12.04.2018, 20:34, "william.croc...@analog.com" :
>>> So, are you saying that the 5.10 branch has been abandoned.
>>
>> No, it's been *closed*. There's a difference.
>
> If it is closed then I assume issues will not be fixed.
> I call that abandoned.
>
>>> If so, I do not think the web site sh
12.04.2018, 20:47, "Thiago Macieira" :
> On Thursday, 12 April 2018 10:34:18 PDT william.croc...@analog.com wrote:
>> >> So, are you saying that the 5.10 branch has been abandoned.
>> >
>> > No, it's been *closed*. There's a difference.
>>
>> If it is closed then I assume issues will not be f
On Thursday, 12 April 2018 10:34:18 PDT william.croc...@analog.com wrote:
> >> So, are you saying that the 5.10 branch has been abandoned.
> >
> > No, it's been *closed*. There's a difference.
>
> If it is closed then I assume issues will not be fixed.
> I call that abandoned.
A closed branch is
So, are you saying that the 5.10 branch has been abandoned.
No, it's been *closed*. There's a difference.
If it is closed then I assume issues will not be fixed.
I call that abandoned.
If so, I do not think the web site should offer it as a download candidate.
Huh, why? What's the rati
On Thursday, 12 April 2018 09:40:46 PDT william.croc...@analog.com wrote:
> On 04/12/2018 11:47 AM, Thiago Macieira wrote:
> > On Thursday, 12 April 2018 04:57:58 PDT Bill Crocker wrote:
> >> Why isn't there a 5.10.2
> >
> > Because we had to kill one branch as we had too many open branches. We
>
On 04/12/2018 11:47 AM, Thiago Macieira wrote:
On Thursday, 12 April 2018 04:57:58 PDT Bill Crocker wrote:
Why isn't there a 5.10.2
Because we had to kill one branch as we had too many open branches. We have
5.6, 5.9, 5.11 and dev left, which is the all-time high except for the few
weeks we al
On Thursday, 12 April 2018 04:57:58 PDT Bill Crocker wrote:
> Why isn't there a 5.10.2
Because we had to kill one branch as we had too many open branches. We have
5.6, 5.9, 5.11 and dev left, which is the all-time high except for the few
weeks we also had 5.10. The developer community came to th
On Thursday, 12 April 2018 01:18:16 PDT Alexander Ivash wrote:
> Is it possible to determine what object is bound to the target object's
> property? Do I understand correctly that bound object should be one of
> subscribers for property's notify signal?
Yes and no. In principle, you're right.
But
You might want to stick with LTS version if you are looking for most stability.
I think the last LTS Qt version was 5.9.x. Qt aim to support a few version
(before it was 5.6.x as LTS). Thoses version should suffer less from major
refactoring or other new features.
Regressions happen. And when they do happen, it hurts, and it bruises the
credibility of our dependencies. The best thing to do is to have test cases at
the ready, and to have them in Qt proper to prevent them. That not always
possible though, so it's important to test the pre-releases. FWICT, Q
Hello:
I have been using Qt-5.7 for a while.
I needed a little help and knew it was no longer "supported"
so I initiated the process of upgrading to 5.10.1
(Yes, it is a process.)
With 5.10.1, one of my apps was crashing and down in a Qt source file.
I knew it could be my fault but, just to
get
Is it possible to determine what object is bound to the target object's
property? Do I understand correctly that bound object should be one of
subscribers for property's notify signal?
Q: Why do you need it?
A: Primarily for debug purposes, but also as the temp solution during redesign
Regards,
23 matches
Mail list logo
