QCoapReply#

The QCoapReply class holds the data of a CoAP reply. More…

Inherited by: QCoapResourceDiscoveryReply

Synopsis#

Functions#

def abortRequest ()
def errorReceived ()
def isAborted ()
def isFinished ()
def isRunning ()
def isSuccessful ()
def message ()
def method ()
def request ()
def responseCode ()
def url ()

Signals#

def aborted (token)
def error (reply, error)
def finished (reply)
def notified (reply, message)

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

The QCoapReply contains data related to a request sent with the QCoapClient .

The finished() signal is emitted when the response is fully received or when the request fails.

For Observe requests specifically, the notified() signal is emitted whenever a notification is received.

See also

QCoapClient QCoapRequest QCoapResourceDiscoveryReply

class PySide6.QtCoap.QCoapReply#

PySide6.QtCoap.QCoapReply.abortRequest()#

Aborts the request immediately and emits the aborted(const QCoapToken &token) signal if the request was not finished.

PySide6.QtCoap.QCoapReply.aborted(token)#

Parameters:: token – PySide6.QtCore.QByteArray

This signal is emitted when the request is aborted or the reply is deleted. Its token parameter is the token of the exchange that has been aborted.

Note

If the QCoapReply is deleted while not finished, both aborted() and finished() signal will be emitted immediately before the QCoapReply is destroyed. Given the QCoapReply may have been deleted when receiving the signal, you should not rely on the sender() object to be still valid.