[http kio slave] use QSslSocket instead of KTcpSocket (deprecated)
ClosedPublic

Authored by ahmadsamir on Oct 22 2019, 8:27 PM.

Diff Detail

Repository
R241 KIO
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
ahmadsamir created this revision.Oct 22 2019, 8:27 PM
Restricted Application added a project: Frameworks. · View Herald TranscriptOct 22 2019, 8:27 PM
ahmadsamir requested review of this revision.Oct 22 2019, 8:27 PM

This will compile, but it will only work correctly once TCPSlaveBase has been ported to QSslSocket too.

This will compile, but it will only work correctly once TCPSlaveBase has been ported to QSslSocket too.

If you say so. Anyway, I've started porting TcpSlaveBase. :)

This will compile, but it will only work correctly once TCPSlaveBase has been ported to QSslSocket too.

If you say so.

Well, socket() returns the KTcpSocket that TCPSlaveBase created, so this cast will always return a nullptr.

Anyway, I've started porting TcpSlaveBase. :)

Awesome! There seems to be only one other place that also assumes socket() returns a KTcpSocket (https://lxr.kde.org/source/kde/pim/kdepim-runtime/kioslave/pop3/pop3.cpp#0625).

This will compile, but it will only work correctly once TCPSlaveBase has been ported to QSslSocket too.

If you say so.

Well, socket() returns the KTcpSocket that TCPSlaveBase created, so this cast will always return a nullptr.

I wasn't doubting the validity of what you said, just I didn't see it, until now :)

Anyway, I've started porting TcpSlaveBase. :)

Awesome! There seems to be only one other place that also assumes socket() returns a KTcpSocket (https://lxr.kde.org/source/kde/pim/kdepim-runtime/kioslave/pop3/pop3.cpp#0625).

Yep.

vkrause accepted this revision.Nov 10 2019, 9:30 AM
This revision is now accepted and ready to land.Nov 10 2019, 9:30 AM
This revision was automatically updated to reflect the committed changes.