> Deepal Jayasinghe wrote:
>>> +1 to not providing /atom when we give the URL. But -1 to tacking it
>>> on in the first place. There is no need for the registry API to make
>>> any assumptions about the URL except that it's rooted wherever we're
>>> told. In other words - shouldn't I be able to say:
>>>
>>> Registry R1 = new RemoteRegistry("http://myhost/regRoot";);
>>> Registry R2 = new RemoteRegistry("http://myhost/regRoot/subDir";);
>> Hmm , I think we should create remote registry by pointing to the base
>> URI of the registry and then , we should be able to perform any
>> operation like adding , deleting and accessing the resources by giving
>> the path.
>
> Yes, base URI of the registry MUST be the actual resource path of the
> registry data- that is, it has to be http://myhost/regRoot/resources.
> That's like how things work in SVN .. usually the last bit is repos.
I think the base URI should be the URI of the registry not the URI of
the resource , because once we create a remote registry we can work with
relative paths.
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
