Hi Mitsuru-san!
Thank you for your comment. I guess, ClientToken(Idempotent) implementation is nice idea for API > requester. > > In my opinion, after POST requested, A requester have to stop processing > when it cannot get response, because requester doesn't know what the > resouce created actually. > In this case, retry is bad way, because it might cause create duplicate > resources. > Yes. It is that I really wanted to do. To tell the truth, I had several offline comments that the term "idempotent" is a little vague/ovrestate to describe what I want to achieve. To be more clear, this feature is to introduce an idea of Client Token in AWS to OpenStack. > I think, ClientToken provide the solution. > If resource had been exist, It would skip resource creation by using > ClientToken. > A requester can avoid create duplicate resources using ClientToken in > retry. > > I wish this blueprint would be implement. And I proposed related blueprint: > > > https://blueprints.launchpad.net/heat/+spec/support-retry-with-idempotency > > I hope so :) Sincerely, Haruka Tanizawa
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
