On Sep 13, 2016, at 11:40 AM, Konstantin Tokarev 
<annu...@yandex.ru<mailto:annu...@yandex.ru>> wrote:



13.09.2016, 21:33, "Jake Petroules" 
<jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>>:
 Because the APIs are deprecated by Apple so they would have had to be 
removed/changed soon anyways, especially when an alternative (which is the 
default now) is already available.

AFAIK they cannot remove API from released SDK, and users may choose to use it 
even if it's not latest and greatest anymore.

They can and have before. Anyways, it doesn't matter. The code was unused, 
untested, and was in the way of other things, so its removal is inconsequential.

Also it caused build failure on tvOS/watchOS.

 On Sep 13, 2016, at 11:25 AM, Thiago Macieira 
<thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote:

 The changelog contains this entry:

 - [QTBUG-45031] The NSURLConnection backend of QNetworkAccessManager has
   been removed, since SecureTransport is the default SSL backend on iOS
   and is enabled by default. This means that building with -no-openssl
   -no-securetransport will no longer provide SSL capabilities on iOS.

 WTH? Why are we removing options in a patch release? What happened?

 Is the backend so severely broken that it needed to be removed?
 --
 Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com>
  Software Architect - Intel Open Source Technology Center

 _______________________________________________
 Development mailing list
 Development@qt-project.org<mailto:Development@qt-project.org>
 http://lists.qt-project.org/mailman/listinfo/development

 --
 Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>
 Consulting Services Engineer - The Qt Company
 Qbs build tool evangelist - qbs.io<http://qbs.io>
 ,

 _______________________________________________
 Development mailing list
 Development@qt-project.org<mailto:Development@qt-project.org>
 http://lists.qt-project.org/mailman/listinfo/development



--
Regards,
Konstantin

--
Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>
Consulting Services Engineer - The Qt Company
Qbs build tool evangelist - qbs.io<http://qbs.io>

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to