Build oauth-Server

I want to build an open platform and use oauth.
Until three files are combined. httpblog. csdn. netstarparkerarticledetails19576511, naming convention, oauth1.0
Httpmy. oschina. netphptiger86blog113262http: // www.huiyi8.com/moban/htmltemplate
With httpwww.lwxshow.comthread-40-1-1.html, the name is amazing,
The above two are based on httpscode. Google. compoauth2-php which contains a wealth of documentation.
I learned how to build my own graph. All the pictures I see are biased. (interactions are conducted in the form of sessions. A session should be a request, a response. All the flowcharts I have seen are mixed .)

Oauth1 personal understanding
Author: laohur
Reference: http://blog.csdn.net/starparker/article/details/19576511

Consumer (APP) server (openpplantform) user (resourse owner)

1. create_consumer
(Consumer_key, secret) <-server/create_consumer.php

2. request_token, secret
Client/get_request_token.php-> server/request_token.php
Server/authorize. php

3. access_token, secret
Client/get_access_token.php-> server/access_token.php

4. API
Client/get_api.php-> server/API. php

Oauth1 personal understanding // original file loss, rewriting
Author: laohur
Http://my.oschina.net/phptiger86/blog/113262
The file name is as follows:
Step 1-> get_request_token
Step 2-> get_access_token
Step 3-> get_api

Consumer (APP) server (openpplantform) user (resourse owner)
0. (server) addclient
1. (client) get_request_token-> (server) authorize
(Client) authorize_token <-user authorize
2. (client, authorized_token) get_access_token-> access_token
(Client) <-(server, access_token)
3. (client, access_token)-> (server) API
(Client) <-(server, API, serource)

I want to learn programming by myself and find it really difficult. What can I do? I should do my financial management.