Glen Daniels 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";);...and have both R1 and R2 work? Isn't this how we're expecting to use this for things like Synapse/Axis2 repositories?new RemoteRegistry("http://registrySite/registry/finance/axis2repo";); Thoughts?
Yes agreed- so what we need to use for the base URL of a remote reg is then http://myhost/regRoot/resources .. that's the path that gives "raw" access to the underlying resources and PUT/POST etc. should all work against that. We already support GET against that to return the normal HTTP response containing exactly the original resource and nothing else.
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
