Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This structure defines the mechanism used for stopping an existing transaction and identifying an existing transaction that has been stopped.

Syntax 

typedef struct wtp_abort_tag{
  WAP_PRIMITIVE_ID 
wpiPrimitiveID;
  WAP_PRIMITIVE_TYPE 
wptPrimitiveType;
  DWORD 
dwValidFields;
  BYTE 
bAbortCode;
  WTP_TRANSACTION_HANDLE 
wthTransactionHandle;
} WTP_ABORT;

Members

wpiPrimitiveID

The primitive identifier. The only possible value is WAP_PRIMITIVE_ID_TR_ABORT, as defined by the WAP_PRIMITIVE_IDenumeration. Applications will cast the base structure according to this identifier. It is always present and valid.

wptPrimitiveType

The primitive type. Possible values are any of the values defined for the WAP_PRIMITIVE_TYPEenumeration.

dwValidFields

Bitmask that indicates the valid fields in the primitive, dependent on the value of wpiPrimitiveID. For possible values, see WAP_PRIMITIVE_BASE.

bAbortCode

A code indicating the reason for stopping the transaction. This value is passed transparently. Possible values are listed in the following table.

Value Description

WTP_ABORTCODE_NORESPONSE

User Acknowledgement was requested, but the user did not respond.

WTP_ABORTCODE_NOTIMPL_UACK

The responder does not support User Acknowledgement.
wthTransactionHandle

A handle that identifies the transaction that is being stopped. See WTP_TRANSACTION_HANDLE.

Remarks

This implementation provides a TR-Abort notification to the initiator or responder. This notification indicates that the transaction has ended and there is no point in attempting to send any more data or waiting to receive any more data.

Requirements

Header wap.h
Windows Embedded CE Windows Embedded CE 6.0 and later
Windows Mobile Pocket PC 2002 and later, Smartphone 2002 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.