Although you do definitely have more overhead associated with ODBC
than with other "native" middleware products like Leetech's CSF (there
are probably others, but none come to mind at the moment), if you're
doing interactive queries and updates, you probably won't notice the
difference.  It's when you start doing "batch style" updates that you
really it.  As an example, I ran a stress test against one of my
Cold Fusion demonstration apps that used the ODBCLink/SE driver
and the PARTSDBE Allbase/SQL database.  With a simulated load
of ten clients, I was getting 600ms response from simple single table
retrievals.  Now that's not something grand and glorious, but it is certainly
good enough for most applications.

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (888) 858-EDIT -or- (509) 943-5108
fax:   (509) 946-1170
--


----------
From:  Steve Hanson[SMTP:[log in to unmask]]
Sent:  Thursday, November 20, 1997 5:55 PM
To:  [log in to unmask]
Subject:  Re: [HP3000-L] VB 5.0 and Image databases

<snip>

ODBC is possible, although performance issues with ODBC arise.  Netbase
provides a product to go after Image databases from NT/95.  There's been
mixed response to the MB Foster ODBC products, but they are another
option.
<snip>