| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
Reviewed-by: Thiago
|
| |
|
|
| |
Reviewed-By: TrustMe
|
| | |
|
| |
|
|
| |
Reviewed-By: Thiago
|
| |
|
|
|
|
|
|
| |
The isFinished() method will return true if the reply has successfully
finished or has been aborted.
Task-number: 257349
Reviewed-by: Thiago Macieira
|
| |
|
|
|
| |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
src/network/access/qnetworkaccesshttpbackend.cpp
src/network/access/qnetworkreplyimpl.cpp
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
In some cases, weird timing issues could occur. In those cases, an EOF
was sent twice for the upload data, leading to the HTTP code being
confused and sending the request headers twice.
Task-number: 257662
Reviewed-by: Thiago Macieira
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is possible that finished() function will be called several times,
for example if the user calls QNetworkReply::close() as a result of
the authenticationRequired() signal, the connection will be closed
(which results in emitting a finished() signal), and then the
authentication will be cancelled, which will also try to emit the same
signal, however the connection state will already be set to Finished.
The fix is to just make sure if the finished() signal has already been
emitted by checking if the connection state is not Finished or
Aborted.
Reviewed-by: Thiago Macieira
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Write only local sockets silently disconnected after some time.
Reason: we cannot call PeekNamedPipe on a write only pipe.
Task-number: 257714
Reviewed-by: ossi
Autotest: tst_QLocalSocket::writeOnlySocket
|
| | |
| |
| |
| |
| |
| | |
Cache return value of expensive function.
Reviewed-by: Peter Hartmann
|
| |\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/sql/drivers/ibase/qsql_ibase.cpp
tests/auto/q3sqlcursor/tst_q3sqlcursor.cpp
tests/auto/qsqldatabase/tst_databases.h
tests/auto/qsqldatabase/tst_qsqldatabase.cpp
translations/qt_ru.ts
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Looks like this `&&' was meant to be `||'.
QNetworkProxy::FtpCachingProxy is 5 so it's clearly impossible for type
to be less than 0 and greater than QNetworkProxy::FtpCachingProxy.
Reviewed-by: Aaron Kennedy
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit removes the 100 ms polling timer from QLocalSocket
and replaces it with proper overlapped IO handling.
Reviewed-by: ossi
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Conflicts:
src/network/socket/qlocalsocket.cpp
|
| | | |
| | |
| | |
| | | |
SOCK_CLOEXEC
|
| | | |
| | |
| | |
| | | |
Reviewed-By: ossi
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The SOCK_NONBLOCK, SOCK_CLOEXEC and accept4(2) calls are
Linux-specific. Other platforms get the same behaviour through
emulation.
Reviewed-By: ossi
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Do the timeout handling the right and cross-platform way. The code
that was in QProcess worked only on Linux, where the kernel sets the
remainder in the returned timeval structure.
Reviewed-By: ossi
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Directly put a QRingBuffer from one QRingBuffer to
another QRingBuffer.
Reviewed-by: Thiago Macieira
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
support
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| | |\ \
| | |/ |
|
| | | |
| | |
| | |
| | | |
Reviewed-by: mauricek
|
| | |\ \
| | |/ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
A few "fixes" to make that number go down..
Reviewed-by: Thiago Macieira
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use the QRingBuffer properly when reading known-size, non-chunked,
non-compressed data from HTTP.
Reviewed-by: Thiago Macieira
|
| | | | |
|
| | |\ \ |
|
| | | |\ \
| | | |/
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/network/access/qnetworkreplyimpl.cpp
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes a bug that occured together with a QProgressDialog.
The signal emission was like:
readyRead readyRead readyRead [...] readyRead finished readyRead
Now finished should be properly at the ending of this sequence.
Task-number: 256630
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| | |\ \ \
| | |/ / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change the QByteArray to a QRingBuffer to save re-allocation time.
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/gui/kernel/qapplication_x11.cpp
|
| | |\ \ \ \ |
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
doc/src/qnamespace.qdoc
src/corelib/global/qnamespace.h
src/gui/graphicsview/qgraphicsscene.cpp
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Conflicts:
src/gui/graphicsview/qgraphicsitem_p.h
|
| | |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Conflicts:
src/gui/graphicsview/qgraphicsscene_p.h
|
| | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Conflicts:
src/gui/graphicsview/qgraphicsitem_p.h
|
| | |\ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
Conflicts:
src/corelib/kernel/qcoreevent.h
src/gui/graphicsview/qgraphicsitem_p.h
|
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |
|
