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.
So all paths like /d1 are relative to that path and all AtomPub PUT/POST/DELETEs go against such paths. GET on such a path simply returns the representation of the resource .. and if that resource happens to be a directory then right now we return nothing IIRC. (My suggestion was to have it take you back to the fancy web view so that we don't create yet another non-standard representation of a collection.
I guess we could use an Atom feed as the representation of any directory resource. Hmm. Would that work? Why not?
Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ email: [EMAIL PROTECTED]; cell: +1 650 265 8311 | +94 77 787 6880 "Oxygenating the Web Service Platform." _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
