17488 Posts in 4473 Topics by 1978 members
|
Page:
1
|
Go to End | |
| Author | Topic: | 1784 Views |
-
Webservices API keys
7 June 2007 at 9:06am
I was thinking we should probably agree on a way of storing the API keys so we can share them amongst the projects.
Do you have any ideas of a good table schema for it? -
Re: Webservices API keys
7 June 2007 at 9:53am
That makes sense to me. Typically, we store this sort of information in the _config.php file of the main module for your project (the one with the same name as your project). Using PHP's define function is typically the way to create a constant string for this.
We hope to have the gsoc branch set up in SVN shortly, and adding it to the shared _config.php file will ensure that the other GSoC people have the keys as well.
-
Re: Webservices API keys
7 June 2007 at 2:57pm
The other way to set up configuration options is to create static methods on your application's classes. Something like:
GoogleMapsIntegration::set_api_key('dfadsfasdfasdfasdfasd');
This has the advantage of being easy to spot in an API documentation or by browsing the function listing in the code.
-
Re: Webservices API keys
18 June 2007 at 1:28am
I agree with Sam on the static method implementation. Mashup module classes will follow that standard.
| 1784 Views | ||
|
Page:
1
|
Go to Top |
