summaryrefslogtreecommitdiffstats
path: root/src/scripttools/debugging/qscriptdebuggerstackwidgetinterface.cpp
diff options
context:
space:
mode:
authorShane Kearns <shane.kearns@accenture.com>2011-04-13 17:04:00 (GMT)
committerShane Kearns <shane.kearns@accenture.com>2011-04-13 17:04:00 (GMT)
commitdd8de4c2437397748daba49569cbc7f89a8bfbee (patch)
tree8b99eace88b0b46cd438a56c8ac5377e8cfd9e14 /src/scripttools/debugging/qscriptdebuggerstackwidgetinterface.cpp
parent9af8b63fd730bf29179a08ee53dc99b7e7646bda (diff)
downloadQt-dd8de4c2437397748daba49569cbc7f89a8bfbee.zip
Qt-dd8de4c2437397748daba49569cbc7f89a8bfbee.tar.gz
Qt-dd8de4c2437397748daba49569cbc7f89a8bfbee.tar.bz2
Optimisation - buffer packet read in pendingDatagramSize
In Symbian, the OS function to get the size of a pending datagram also includes the size of the packet header (which is different for IPv4 and IPv6). We were reading the datagram with the "peek" flag set to implement pendingDatagramSize, then reading again normally when the client called read/readDatagram. This change removes the "peek" flag, and buffers the datagram in the socket engine, returning it and clearing the buffer when read or readDatagram is called. If there is no buffered data, the existing code path is followed - it isn't mandatory to call pendingDatagramSize before reading from the socket. Reviewed-by: Markus Goetz
Diffstat (limited to 'src/scripttools/debugging/qscriptdebuggerstackwidgetinterface.cpp')
0 files changed, 0 insertions, 0 deletions