Jeremy Boynes wrote: > Think of the carnage if it was java_14208_b13.sql_300.Connection
It's actually instructive to look how Java solves this: - The interface is kept upwards compatible, by following rules such as only new methods/fields etc. Then to look at how a consumer, Derby, deals with the fact of multiple versions of the interface: - Derby only provides and uses the functionality to match the version of the interface (java.sql.Connection) loaded, determined at runtime. I'd thought this was a workable direction being proposed about six thousand message ago, upwards compatible apis and the ability for a consumer to handle a lower version. Not sure what derailed it. Dan.
