Kathey Marsden wrote: Oops typos and another question.
>> >> >I am sorry that I cannot provide any insight on why the DataSource >implementations implement Rerferenceable > [insert ] in this way >, except to say that I think >it is good that you seem to be taking a fresh look at it in terms of >what we need for Derby. > > > >>I would suggest instead that we use one StringRefAddr to store the >>address with the value being a URL with suitable parameters set (i.e. >>as used by the Driver). >> >>Ultimately, this will allow us to have references that point to >>multiple addresses (e.g. in a federated server) >> >> >> >Just some questions. Not educated enough in this area to comment yet #:) >Could you explain the federated scenario in more detail and how the >referenceable DataSource would come into play? Also my JS169 red flag >went up when I saw "URL" and "Driver". I was wondering are there >JSR169 implications in doing this? > > > How does this all relate to the embedded implementation of Referenceable? I ask because in general I would like to see the client Driver merge as much as possible with the embedded behaviour. Thanks again Kathey
