#19 closed task (fixed)
Port network module
Reported by: | Dmitry A. Kuminov | Owned by: | Dmitry A. Kuminov |
---|---|---|---|
Priority: | blocker | Milestone: | Qt Beta 2 |
Component: | QtNetwork | Version: | 4.5.1 Beta 1 |
Severity: | Keywords: | ||
Cc: |
Description
Provide an OS/2 version of the platform-specific classes from the network module and enable it.
This includes porting the following classes:
- QHostInfo
- QNetworkInterface
- QNetworkProxy
- QLocalServer
- QLocalSocket
- QNativeSocketEngine
Change History (8)
comment:1 by , 15 years ago
Component: | General → QtNetwork |
---|
comment:3 by , 15 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
comment:4 by , 15 years ago
Unix implementations of QNativeSocketEngine, QLocalServer and QLocalSocket should work fine on OS/2 so we will use them (with some tiny modifications such as ripping off IPv6 support) so far.
comment:5 by , 15 years ago
QHostInfo and QNetworkInterface are implemented based on the Unix port as well. The only problem is that there is no SIOCGIFHWADDR support in kLIBC (or in the OS/2 TCP/IP library itself?) and therefore we can't get the hardware address of the interface through the ::ioctl API (and hence QNetworkInterface::hardwareAddress() will return an empty string on OS/2 at the moment). I've created #63 to solve this minor problem later.
Other than that, the network module seems to build fine. I'll perform some functional testing tomorrow before closing this defect.
comment:6 by , 15 years ago
Fixed a number of socket notifier related bugs in r161. The network classes seem to work now, successfully tried examples/network/fortuneserver, fortuneclient and ftp.
Therefore, I will release Beta2 tomorrow with the network module included.
comment:7 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
comment:8 by , 15 years ago
Milestone: | Qt GA → Qt Beta2 |
---|
This is kind of important for the GA since 90% of applications use the network in some or another form these days.