Hello all
We currently have a "storage" group with, for now, a single module:
sis-netcdf. This module contains about 3 classes which are not
NetCDF-specific, but would rather be common to every storages. Those
classes are:
* DataStore (not yet committed)
* DataStoreException (in public API)
* ChannelDataInput (for internal SIS usage only)
I was planing to leave those classes in the sis-netcdf module for now,
and wait to have a second storage module before to factor out the common
part. However I realized that this have a slight impact on the way the
tests are written, so maybe it would be better to settle down the above
classes in their right location right now... They could be in a
"sis-storage" module, to be created. The inconvenient is that it is a
little bit strange to create a whole new module for only 3 classes, but
this module would certainly growth in future SIS versions.
Any though?
Martin
P.S.: I said last week that I would post a proposal for a DataStore
interface. I'm late again, but will try to post it this week.
