Generic response
Int32
—p_operation
-
Operation code
If operation equals op_response
— 9
:
Int32
—p_resp_object
-
Object handle
Although 32-bit in the protocol, valid handle values are always between 0 and 65535 (0xFFFF), with the “normal” range between 0 and 65000, where
0
either represents the connection itself, or means “no value”. Int64
—p_resp_blob_id
-
Object ID
Buffer
—p_resp_data
-
Data (meaning depends on the operation).
Byte[]
—p_resp_status_vector
-
Status vector
The format of the status vector is
<tag><value>[{tag><value>} ...]<end>
, with<tag>
anInt32
, and where parsing of<value>
depends on<tag>
;<end>
isInt32
isc_arg_end
—0
.The length can only be determined by correctly parsing the status vector.The first 8 bytes are always anInt32
tag (isc_arg_gds
orisc_arg_warning
) and anInt32
value.-
If the status vector starts with
Int32
isc_arg_gds
—1
and the secondInt32
is non-zero, it is a failure response. -
If it starts with
Int32
isc_arg_warning
—18
and the secondInt32
is non-zero, it is a success response with warning(s). -
Otherwise, if the second
Int32
is zero, it is a success response
ImportantInformation about parsing the status vector can be found in the Interbase 6 API Guide in the documentation set.It might also be advantageous to look at the sources of {net-provider-repo} or {jaybird-repo}.
-