ODBC has annoyed me for a very long time, at least 7 years. Suffice it to say
that it is an interface, not a protocol, where a protocol standard would have
been very appropriate.
Of course this has led to no end of headache, incompatibility, cost, vendor
lockin, poor performance, etc.
Seeing as how all database activity can be handled with a SOAP style API
(command, arguments, and zero or more responses as a stream of possibly
different 'rows' and status), why haven't we (or I at least) heard of SOAP-DB
One issue would be that some things in the ODBC API are best handled locally,
but that's fine with me. Doesn't have to follow an outdated API directly; in
fact I would welcome a redesigned DB protocol/API. In particular, it MUST
have the capability of streaming/pipelining when the remote system can handle
-- firstname.lastname@example.org email@example.com swilliams@Jabber.com Stephen D. Williams Insta, Inc./Jabber.Com, Inc./CCI http://sdw.st 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax Dec2000
This archive was generated by hypermail 2b29 : Fri Apr 27 2001 - 23:17:45 PDT