When closing a query, if connection is closed, consider the request was successful

[kadishmal]

According to CUBRID CCI native driver implementation function qe_send_close_handle_msg(), we can consider the connection closed operation as a successful request.

This is true because internally CUBRID Broker manages a pool of CAS (CUBRID Application Server) processes. When a client connects, the Broker assigns/connect it to one of the CAS. Then the client sends some query requests to this CAS. After the client receives a response, it may decide to do some other application logic before it closes the query handle. Once the client is done with the response, it may try to close the query handle.

In between these receive response and close query, CUBRID Broker may reassign the CAS to another client. Notice the client-Broker connection is not broken. When the actual close query request arrives to the Broker, it finds out that the CAS referred by the client is reassigned, it sends CONNECTION RESET to the client. node-cubrid should listen it and consider such event as if the close query request was successful.

Need to check if this is the same for close connection and other similar requests.