| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
QLocalSocketPrivate::bytesAvailable has been renamed to
QLocalSocketPrivate::checkPipeState to match the purpose of this method.
Reviewed-by: ossi
|
|
|
|
|
|
|
|
|
| |
Reading from a socket with a broken connection didn't work, even if
there were still bytes to read in the internal read buffer.
Autotest: tst_QLocalSocket::writeToClientAndDisconnect
Task-number: QTBUG-10921
Reviewed-by: ossi
|
|
|
|
|
|
|
|
|
| |
Don't call GetOverlappedResult if ConnectNamedPipe connects instantly.
Autotest: tst_qlocalsocket::threadedConnection
Task-number: QTBUG-8477
Done-with: ossi
Reviewed-by: ossi
|
|
|
|
|
|
|
|
|
|
|
|
| |
qt_safe_write and and qt_safe_read already contain EINTR_LOOP.
It seems that this loop has been added to code due to
merge/clean-up errors in commits:
4aafbd6222e7aeafd59a4a4356ba8c53b2bfa1d1
f0a8feed9e9b4de10df76faa350201edaef98f1d
Reviewed-by: Aleksandar Sasha Babic
Reviewed-by: Markus Goetz
|
|
|
|
|
|
|
|
|
| |
If _q_onNewConnection failed, then QLocalServer got into a bad state.
QLocalServer::isListening() still returned true and
QLocalServer::close() crashed.
Task-number: QTBUG-10388
Reviewed-by: ossi
|
|
|
|
|
|
|
| |
If we're not even going to connect, there's no point in trying to get
the host resolution
Reviewed-By: Markus Goetz
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/qt-s60-public:
Fixed app freeze if switching to offline in middle of HTTP transaction.
Document Symbian platform security requirements on Qt APIs
Fixed app freeze if switching to offline in middle of HTTP transaction.
Removed QtDeclarative.dll deployment from qt.iby in 4.6 branch.
Don't build QtXmlPatterns' command line tools on Symbian.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Work done jointly by Gareth and me. Yields no qdoc errors.
Task-number: QTBUG-9342
Task-number: QTBUG-9120
Reviewed-by: Gareth Stockwell
Reviewed-by: David Boddie
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When active socket is disconnected by swithcing to offline mode, native
RSocket completes the active socket operations with KErrCancel (-3).
Open C maps this error code to POSIX errno EINTR (4). Normally in Posix
EINTR is only used to indicate that some operation was interrupted by
POSIX signal. Qt has a while loops in network operations to handle
operations interrupterd by signals. These while loops will be
effectively forever loops in Symbian due to Open C error code mapping.
Because Symbian does not have native support for signals, i.e. the
network operations can never be really interrupted by POSIX signal,
it is ok to remove these while loops completely on Symbian platform.
This fix is a workaround to Open C incorrect error mapping, and
should be removed once Open C has fixed their error mapping.
Task-number: QT-3274
Reviewed-by: Aleksandar Sasha Babic
|
|/
|
|
|
|
|
|
| |
When closing a QLocalSocket, which has unwritten data, the pipe writer
was never deleted. Thus writing after a reconnect didn't work.
Task-number: QTBUG-9681
Reviewed-by: ossi
|
| |
|
|
|
|
|
|
|
| |
Use qt_qhostinfo_lookup which avoids the event loop when the DNS
result is already cached.
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: ossi
|
|
|
|
|
|
|
|
|
| |
Destroying a QLocalSocket with unwritten data left unclosed handles
behind. The connection wasn't closed properly, such that the other
end didn't get notified about the connection loss.
Task-number: QTBUG-7815
Reviewed-by: ossi
|
|
|
|
|
|
|
|
| |
We had some bugreports and support requests related to
misunderstandings about this.
Reviewed-by: Peter Hartmann
Reviewed-by: David Boddie
|
|
|
|
|
| |
Reviewed-by: joao
Reviewed-by: Peter Hartmann
|
|
|
|
| |
Reviewed-by: thiago
|
|
|
|
|
|
| |
Task-number: QTBUG-7316
Task-number: QTBUG-7317
Reviewed-by: thiago
|
|
|
|
| |
Reviewed-by: thiago
|
|
|
|
| |
Reviewed-by: joao
|
|
|
|
|
|
|
|
| |
We had an hack in the code that chunked writes. Try to avoid
this since the hack is probably only needed for older windows versions.
Task-number: QTBUG-7344
Reviewed-by: Peter Hartmann
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
There was a buffer that is always empty since it was only used for
parsing the HTTP proxy protocol, not the actual socket data.
Reviewed-by: Peter Hartmann
|
| |
|
|
|
|
|
|
| |
Let's see if this happens.
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
|
|
| |
The select() system call was used in the wrong way.
We need to select for exceptions too.
Task-number: QTBUG-5799
Reviewed-by: Aleksandar Sasha Babic <aleksandar.babic@nokia.com>
Reviewed-by: Peter Hartmann
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... as described in the documentation. Furthermore:
* use qt_safe_select to timeout correctly
* return immediately when timeout value is 0
Reviewed-by: Oswald Buddenhagen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a timeout that occurred on Mac with the gui event dispatcher:
we were waiting for a write notification, but timed out when we were in
closing state and still waiting for the socket engine to complete
writing.
Now we close the socket anyway after 2 seconds.
Reviewed-by: Thiago Macieira
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
only disconnect from host when all bytes have been written; i.e. not
only check whether the write buffer is empty, but also check whether
the socket engine has still bytes to write. This is necessary for
HTTP and SOCKS5 socket engine, because they both contain an inner TCP
socket which also does buffering. For the native socket engine, there
is no difference with this patch.
Reviewed-by: Markus Goetz
Reviewed-by: Thiago Macieira
|
| |/
|/|
| |
| |
| |
| |
| | |
the indexOf() call did not consider actualReadBufferSize and thus
scanned uninitialized memory for newlines.
Reviewed-by: phartman
|
|/
|
|
|
| |
Task-number: QTBUG-4984
Reviewed-by: Thiago
|
|
|
|
|
|
|
| |
Handle setSocketOption and forward it to the plainSocket that
QSslSocket is using internally.
Reviewed-by: Thiago
|
|
|
|
|
|
| |
After 4.6 API review.
Reviewed-by: Volker Hilsheimer
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out that if socket was signalized via exception fds
set, we should signalize only write notifier in the case where
both read and write notifiers exist.
If in this case we send signal to read notification socket will
prematurely be closed.
x#Reviewed-by: Janne Antilla
|
|
|
|
| |
Workaorund for SO_REUSEPORT / SO_REUSEADDR regression bug.
|
|
|
|
|
|
|
|
| |
receiving the WSAEMSGSIZE error means we could not read all the data
because the buffer was too small, but still we should return the number
of bytes read and not return -1
Reviewed-by: Marius Storm-Olsen
|
|
|
|
|
|
|
| |
If pipeClosed is true, then we've already emitted the
readChannelFinished signal. We must not do this in close() in that case.
Reviewed-by: ossi
|
|
|
|
|
|
|
|
| |
If we've detected a broken pipe and we have no more data in the
read buffer, then we return -1 to signal EOF.
Additionally, we close the QLocalSocket.
Reviewed-by: ossi
|
|
|
|
|
|
|
| |
If we detect in a read operation that the pipe has been closed,
we must emit the readChannelFinished signal.
Reviewed-by: ossi
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
| |
Have QWindowsPipeWriter emit a bytesWritten signal and have
QLocalSocket connect this to its own bytesWritten signal.
This change contains an autotest to check for the signal emission.
Previously there was no implementation to emit the signal.
|
| |
|
|
|
|
|
|
|
|
|
| |
If the server disconnects directly after writing its data, like the
localfortuneserver example does, we must close the reading client
socket. Before this patch, an error was yielded.
Task-number: 260631
Reviewed-by: phartman
|
|
|
|
|
|
| |
... but leave it there on Symbian.
Reviewed-by: Aleksandar Sasha Babic
|