Dear Volker,
I have always found Qt project fascinating from a technological
perspective. I enjoy using it and I will surely continue to do so. Multiple
times when I discovered that some things can be made faster, better or more
robust I felt the need to give the community something back.
Unfortu
For some reason I also started getting them directly to the SPAM folder on
my GMall account.
>From interest, dev but not from qt-creator MLs
pon., 14 gru 2020 o 07:14 Roland Hughes
napisał(a):
> Messages are really short. Some have just one short email in them. This
> isn't the typical size prob
s on the Qt Essentials to make them as good as possible for Qt 6. So I expect that we’ll have a fully supported web sockets module available for Qt 6 by the time 6.1 or latest 6.2 is being released. Cheers,LarsOn 26 Jun 2020, at 14:23, Narolewski Jakub <izow...@gmail.com> wrote: Hello :]Lurking y
Hello :]
Lurking yesterday on a dev mailing list I accidentally stumbled upon topic
that mentioned this wiki site:
https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion
As I understand it, it is a listing of Qt modules and their their 'cmake
porting progress' and I quote:
"Given the deadline for the
Just fixing small typo in my last email.
"Typically there are around 108 clients per server instance"
pon., 3 lut 2020 o 21:37 Narolewski Jakub napisał(a):
> Hello :]
>
> I had some time to do more tests experimenting with custom event
> dispatchers.
> To give more b
Last email was probably eaten by hungry mailing list - resending it just in
case!
Hello :]
I had some time to do more tests experimenting with custom event
dispatchers.
To give more background, my use case is as follows:
1. There is one main thread - 'Server' - that currently contains
QWebSocket
l. So there's a second place to deal with
> registering/unregistering, aside from QSocketNotifier.
For the love of God I can't find it. Do I understand correctly, that I
should look for another place that call register / unregister
SocketNotifier() directly?
niedz., 19 sty 2020 o 17:57 N
, 30 gru 2019 o 22:00 Thiago Macieira
napisał(a):
> On Monday, 30 December 2019 15:31:14 -03 Narolewski Jakub wrote:
> > I did not notice if unregisterTimer() and registerTimer() are also called
> > so often but their non-destructive switching could also come in handy.
>
This sounds like a great idea :]
So, as a consistency is a prime property of every cake, in case of sockets
this could be pair of:
QAbstractEventDispatcher::enableSocketNotifier()
QAbstractEventDispatcher::disableSocketNotifier()
I did not notice if unregisterTimer() and registerTimer() are also
Answering my own question - QSocketNotifier gets unregistered in the event
dispatcher every time QSocketNotifier::setEnabled(false) is called.
Additionally, QSocketNotifier::setEnabled(false) is called after every
write event on the descriptor. As I was sending data 20 times per second
throught my
My first email was scrubbed to HTML attachment - I'm resending it form
different email client in hope of better visibility on the mailing list.
I have this pet project of mine in which I'm testing the possibility of
integrating libuv's event loop cleanly with Qt.
After some research I come to conc
Although all these examples look nice the CMAKE_VERBOSE_MAKEFILE is good
enough for me as I currently develop my software remotely using VS Studio
and it's remote CMake integration. I just modify CMakeSettings.json and
there comes more stuff to read :)
On Mon, 26 Aug 2019, 17:32 Matthew Woehlke,
More recent discussion about this problem can be also found at:
https://bugreports.qt.io/browse/QTBUG-58237
On Thu, 4 Apr 2019, 21:35 Jason H, wrote:
> Yes. Gone are the days of security from obscurity. Minutes after standing
> up a AWS ec2 instance i was getting scanned. Easy way to get rid o
t checks are bad form. There's no reason for it to end
> with, it should probably be using contains()
> > >
> > > 3. There are multiple `if` blocks that don't set an error. This isn't
> wrong, as the handhake bytes may come in slowly and take multiple
> re-parsings, (someth
That's the thing. I already handle connections and disconnections in my
code - including logging relevant information.
When I implemented this I heavily based on the example that you linked to.
WSS communication is single threaded - only way to communicate with the
outside world from different thre
15 matches
Mail list logo
