-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorry for troubling you again....But I really need your help~ #4
Comments
Hi, I don't know much about Windows or Sina Weibo, but here are my O2 related answers ~ Akos. On Feb 6, 2013, at 14:04, SSSANTON notifications@github.com wrote:
Because O2ReplyServer is a complete web server. That's how you write network servers in Qt.
This is the method that initiates logging in. So when the user presses the login button for example, you should call this method
That's a default URL which works for most OAuth providers. You can have a custom one, if Sina Weibo requires it. See the Skydrive customization for example in o2skydrive.cpp.
All these need a web UI which you must provide by opening a browser window with the given URL. But the rest of the interaction will be taken care by the service provider.
And you don't even need to deal with code and token yourself, if you are using the O2 library for creating authenticated requests, using O2Requestor and O2Reply. O2Requestor is like QNetworkAccessManager, but instead of sending plain network requests, it creates and sends authenticated requests. O2Reply is like QNetworkReply, plus it handles network timeouts and expired tokens.
|
Hi! My friend Akos: I can't overcome the problems and keep my patience without your generous help! So I have to thank you again! |
After reading the lastest README doucument you just uploaded,I still can't use this library to make an Open Platform Client(Sina weibo, like facebook) through oauth2 authorization which based on desktop(win7) enviorment.Is that this library not support in desktop application?
According to my poor knowledge about network and HTTP methods.I learnt that the o2reply is use for deal with the QNetworkreply queue.And the o2replyserver is use for handle the data from the TCP socket.At last,the o2requestor is for GET or POST with the token to use the API.But what make me painful is how all these stuff works in a project.I really want to know is the procedure of the the library(very hopeful).
1.Why it use the TCP instead of the QNetworkReply for processing the Authorization Reply?
2.
(1)What is the purpose of O2::LINK?
(2)Why the RediretUrl is http://localhost:%1/").arg(replyServer_->serverPort()?Can I change it which I had setted on callbackURL setting of the platform I used?
(3)It that right once the SIGNAL openBrowser(url) is emited,the newconnection from QTCP will be emitted?It's that means that we open the brwoser(Qurl) just for get response from the TCP port and have a TCP newconnecttion?If is is not?And how to active the SIGNAL newconnection?
(4).All the problems troubles me,because it is impossible to get the "CODE" with for acces the TOKEN. without sloving these problem.And could you please give me some advice for getting the CODE from the firt step of the oauth2.0 protocol.
Anyway,no matter you answer all these problems or no,still thanks for share such wonderful oauth2.0 library based on QT,cause such properties is extremly less.And all these problems may only for one reason------I am a typical noob~~~ orz
The text was updated successfully, but these errors were encountered: