A user at Informix writes:


Hi Seth,

Yeh-Heng Sheng (Mg of Informix ESQL/C and JDBC development)
gave me your email address as an influential contact at JavaSoft.
I apologize for the somewhat alarming email subject line, but
I wanted to get your attention. If you are like me, you must be getting
over 200 emails per day!!

    I need to interface our Java Socket based Type4 JDBC client driver to our
legacy Informix database server process which happens to use TCP expedited
data as an out-of-band signaling mechanism for canceling queries.
In order to be 100% application protocol
compatible, our Java JDBC driver would have to be able to send a one byte
expedited TCP data message to the database server along with sending/receiving
the standard normal-flow (in-band) TCP SQL protocol messages.
The one byte expedited TCP data message is used by the database server as a
mechanism for detecting the client wishes to cancel the current SQL request
in the SQL session associated with the TCP connection.

    This cannot be done given the current 1.1/1.2
Java API Java.net.Socket class methods. I would have expected the
Java.net.Socket class to contain the equivalent of an expedited
output stream accessor method such as getExpeditedOutputStream()
which would return a traditional Java OutputStream
object. This would then be usable to send expedited messages. Though there
have been substantial enhancements in the 1.1/1.2 Socket class such as the
addition of setTcpNoDelay() (critical to buffered TCP performance) THERE
IS NO CAPABILITY IN THE Java API FOR SENDING TCP EXPEDITED DATA !!!

After exchanging email with various other Java developers
in several of the Java newsgroups, I have concluded that Informix
is not alone in needing to interface Java.net.Socket based clients
to legacy servers which happen to use TCP expedited data. If
JavaSoft is serious in promoting Java based application clients which
access legacy TCP based servers, JavaSoft would sooner or latter have to
offer some way for TCP clients to send expedited data.

I hope you can provide me with additional email contacts at JavaSoft/Sun
who are directly responsible for the Java.net.Socket class implementation.
Perhaps you yourself as well may be able to forward this email to the
appropriate individuals, clarifying the usefulness and urgency of our
request. As things currently stand, the Informix Type4 JDBC driver
will not be able to cancel SQL queries when connected to our any of our
customer's currently installed Informix database servers unless sending TCP
expedited data is supported by the base Java.net.Socket implementation.


    Any help, suggestions , or comments (other than changing the legacy or
future Informix database servers in one of many possible ways) would be
greatly appreciated !!!!
    
    Thanks in advance,

        Jorge

    
 __________________________________________________________________________
| Jorge Noa, Communications Architect INTERNET : ###@###.### |
| Informix Software, Inc. UUNET : uunet!infmx!jnoa |
| 4100 Bohannon Drive VOICE : (415) 926-6096 |
| Menlo Park, CA 94025 FAX : (415) 926-6571 |
|__________________________________________________________________________|
| In addition to NULL, SQL3 data attributes will include CHARM and COLOR ! |
|__________________________________________________________________________|