I got a message that I would like to answer via the list, for everybody's
benefit (I'm doing a Bcc to the contributor).
 
>...  I would think there would be
>some advantages in making ADBC look as much like JDBC as possible
 
Correct.
 
>(though this may be tough as JDBC is of course an RDBMS based thing.
 
Correct (I assume you mean "going through the SQL fat" when you say "an
RDBMS based thing").
 
So, our challenge is to take the best of JDBC and to streamline it
according to the needs of our objective: "to provide the most direct path
possible from a Java-enabled client to IMAGE data, through the IMAGE
intrinsics".
 
 
>>        3) A prize for the best implementation of ADBC.
>
>Best implementation *of* ADBC itself, or the best application *using*
>ADBC?
 
As a first step, ADBC itself.
 
Once we have successfully implemented ADBC (the technology), we can begin
to deal with applications *using* ADBC.
 
I would venture to say that APPLICATIONS providers would be interested in
running their own applications-oriented contests :-)
 
 
>>ADBC is a collection of Java classes whose function is to provide the
>>shortest possible access path between a client application on any
>>device (that supports Java) and IMAGE databases (on HP3000 computers).
>
>Ok, so, like, do you have a spec or something yet?
 
I know what I want ("to put a man on the moon in x years and to bring him
back alive" or words to that effect).  Defining the exact detailed specs
for implementing the ADBC technology is our first step.
 
You may think of the ADBC contest as a "request for comments" (RFC).  This
has to be a community effort.  Your specific points are an excellent start.
 
 
BTW: I did not mention your name today, out of respect for your privacy.
If you authorize me, I'll be delighted to mention the names of the
contributors (which I would like to be the default).  So, everyone, please
let me know what you prefer whenever you communicate with me.
 
 
>... I'd like to see how
>you address the security issue, as from my experience it is very
>difficult if not impossible to design an API that is both callable from
>an un-trusted system and yet provides Image intrinsic level access to
>data, since Image's password scheme falls down when a "user" is one of
>12,000 students wanting to access their grades, etc.
 
You have been talking with Eric Schubert of Notre Dame, I see :-)
 
DCE (or acronyms to that effect) would be nice.  But we can't wait for HP
to implement it (or anything else, for that matter) on the HP3000.  Any
suggestions for things we can do NOW?
 
We can always leave the 12,000-student issue for the second release :-)
 
 
 
>Best regards,
 
Thank you.  Likewise.
 
+---------------+
|               |
|            r  |  Alfredo                     [log in to unmask]
|          e    |                           http://www.adager.com
|        g      |  F. Alfredo Rego               Tel 208 726-9100
|      a        |  Manager, Theoretical Group    Fax 208 726-2822
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
|               |
+---------------+