It was meant to be renamed later during Derby client development, but
fell through the cracks. All the code in AM directory implement JDBC
interfaces that are not public. May be 'Client.impl' may have been a
better choice, instead of 'Client.am'.

Satheesh

David W. Van Couvering wrote:

>
> Does anybody know what "am" stands for, by the way?
>

Reply via email to