Inband breaks are (were) not supported by all protocols and not all
implementations of the same protocol on each platform (especially in the
early days of SQL*Net). It was clear to the developers that OBB was the most
optimal way of implementing break handling but not every platform did
Hi,
Or may be because IBB is in the queue, that why it seems like not working.
Just my speculation
Sinardy
-Original Message-
Sent: 18 March 2003 17:09
To: Multiple recipients of list ORACLE-L
Inband breaks are (were) not supported by all protocols and not all
implementations of
Out of band breaks are pimarily used to cancel a query or transaction. In
the new OCCI, out of band breaks corresponds to the cancel method in the
ResultSet class or terminateStatement in the Connection class. I
sort of hate this stuff. Those things used to be called ocan and obreak
and OCCI
The main difference between INB OOB breaks is that the Oracle kernel will
get notified directly when OOB is received (a bit is set to indicate that an
interrupt happened and the Oracle kernel will check this bit every now and
then). With in band breaks the connections has to be tested (real
Nope,
This will just cancel the current query *AFTER* a fetch. What you describe
means that you need to run with non-blocking oci.
Anjo.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, March 18, 2003 3:44 PM
Out of band breaks are
Hi all,
I have question about Inband break, please help me understand this
Oracle said:
There are 2 types of breaks:
- Inband breaks: are transmitted as part of regular data traffic using the normal
protocol read and write functions. These breaks are symply queued.
- Outband breaks: are
