[bind10-dev] Return codes for RESTful API

[Michael Graff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just another quick note here...  "commands" are not really what you
expect to see in a RESTful API.  That is, http://site/zone/add is not a
command, but the URI would alter configuration.

I'm a RESTful purist as much as that is possible.

- --Michael

On 2010-05-24 3:51 AM, zhanglikun wrote:
> 　Hi all, I am working on http return codes of RESTful API, try to gather
> more information by sending this email. 
> 　The RESTful API of cmdctl was designed like:URL:
> /module_name/command_name, command paramters are sent with post-data. 
> 　Currently we don’t have a well-defined status rcodes list, if one command
> sent from bindctl isn’t executed properly, some error message may be
> printed by bindctl, which depends on whether the aim module provide
> well-defined rcode and error message(anyway, we have defined the command
> reply format, see
> https://bind10.isc.org/wiki/ModuleConfigurationCommunication).
> 
>   There are two types of status rcode in my opinion:
> 1. Well categorized status rcodes.  
>   Like http status rcodes.
>   500 Internal Server Error
>   400 Bad Request
> 
> 2. Define unique rcode for different command.  
>   Like the rcode in oracle: ORA-12504: TNS:listener was not given
> SERVICE_NAME -- ASP.NET Connection
>       
> I think it's easy to locate the error if using the second way.
> 
> Any suggestion?
> 
> Thanks
> Zhang Likun
> 
> 
> _______________________________________________
> bind10-dev mailing list
> bind10-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind10-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkv77+UACgkQ+NNi0s9NRJ1mEACeMYwF88m/e3Wp5ZZUXGHQDQxA
LsYAniyIbeX1EpNcssrchh69BSD1XDSd
=Kmbg
-----END PGP SIGNATURE-----