[udig-devel] ID / Connection Params / Credentials

[Jody Garnett]

I am going to keep ranting before I forget... some other points to this 
discussion, we are in fact out growing our definition of ID:
- the same service should have the same id; even if a project is making 
use of different connection parameters to talk to it; easiest example is 
the connection parameters that represent the credentials (say user name 
and password). We have always wanted to store the credentials in a 
separate service; I had not thought of making that service map specific 
(but perhaps that is useful?)
- this is related to the split between identify (ie conneciton 
parameters) and configuration (the rest of the connection parameters). 
As an example you can connect to the same shapefile using 
IndexedShapefileDataStore or ShapefileDataStore by changing the index 
connection parameter. The same IGeoResource handle can support both 
instances at once; although we would need to inject a common Lock object 
so they do not deadlock while writing to the same file.
- We have had some experience internally with a catalog making use of 
two IDs; one for the ServiceID and one for the ResourceID; this makes it 
much easier to simply move the Service; and have all the resources come 
along for the ride. Chances that an ID for the type of content would 
also be good (although that breaks my head).

Cheers,
Jody