+1 .. also, I'd *really* like a GET on the old path to result in a 304
Moved Permanently HTTP response ..
Sanjiva.
Deepal Jayasinghe wrote:
+1 from me too, although we need to think carefully about how this new
functionality gets exposed via the APP interface. In particular, I
think we need to support a rename/move as a *single* remote operation,
triggered by a POST somewhere....
Yes that what is I am planing to.
-Deepal
--Glen
Sanjiva Weerawarana wrote:
+1.
Sanjiva.
Deepal Jayasinghe wrote:
Hi all ,
I have implement the resource rename in my local machine , but that to
be useful I think we need to change Registry API to have the
renameResource or moveResource method . Is that ok if I go ahead and
add
that and commit the code ?
-Deepal
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
--
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
