What happened to 35357?
In general, new port #s should be applied through IANA and when approved then
made public.
Peter.
-Original Message-
From: openstack-bounces+peter.mellquist=hp@lists.launchpad.net
[mailto:openstack-bounces+peter.mellquist=hp@lists.launchpad.net] On Behal
I understand the benefits of being able to generate docs and specs from code
since it ensures that these are in synch and that the specs follow what the
code supports but ... in regard to API design this approach leaves something to
be desired. There is much value in designing the APIs up front
This is an Internet-Draft hence it can still be changed or removed. Additional
status codes are a good thing but .. if the proposal is to implement a draft
like this within services, middleware and clients before it is a full standards
track RFC this can might cause issues if changes occur. BTW,
Excellent topic Joe, thanks for bringing this up.
There are two main perspectives on WADLs: WADLs from a service developer point
of view and WADLs from a cloud developer point of view. I consider the later
the most important since we need to ensure that developers who write all the
killer Opens
Looking through the latest Keystone code and developer guide I have noticed
some differences in the usage of PUT and POST CRUD operations.
Resource Creation admin.py Developer Guide Says
Tenant PUT
The latest github source and tars no longer have any WADL or XSDs? ( looks like
the symlinks now point to non-existent directories ).
https://github.com/rackspace/keystone/tree/master/keystone
I am interested in looking at the latest identity.wadl and XSDs.
Thanks,
Peter.
__
6 matches
Mail list logo
