| Total Complexity | 5 |
| Total Lines | 18 |
| Duplicated Lines | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 3 | class OAuthDataStore { |
||
| 4 | function lookup_consumer($consumer_key) { |
||
|
|
|||
| 5 | // implement me |
||
| 6 | } |
||
| 7 | |||
| 8 | function lookup_token($consumer, $token_type, $token) { |
||
| 9 | // implement me |
||
| 10 | } |
||
| 11 | |||
| 12 | function lookup_nonce($consumer, $token, $nonce, $timestamp) { |
||
| 13 | // implement me |
||
| 14 | } |
||
| 15 | |||
| 16 | function new_request_token($consumer, $callback = null) { |
||
| 17 | // return a new token attached to this consumer |
||
| 18 | } |
||
| 19 | |||
| 20 | function new_access_token($token, $consumer, $verifier = null) { |
||
| 21 | // return a new access token attached to this consumer |
||
| 22 | // for the user associated with this token if the request token |
||
| 23 | // is authorized |
||
| 24 | // should also invalidate the request token |
||
| 25 | } |
||
| 28 |
Adding explicit visibility (
private,protected, orpublic) is generally recommend to communicate to other developers how, and from where this method is intended to be used.