-
Notifications
You must be signed in to change notification settings - Fork 378
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
update code for 2gb filesize limit #88
Comments
Which commit contain your change? I can't find it in github. On Tue, Jul 10, 2012 at 6:21 PM, indian4646
|
I am sorry for this, could you check again, https://github.com/indian4646/grive |
Thanks. Your patch is very interesting. I see you passed the OAuth to Resource and Refresh() it. Why is that needed? Please dont cast OAuth to http::Header. It may not work. Please change CStdioFile to fopen64() instead of calling it directly. |
This code maybe for your reference, because I have tested this code can work to support 2G limit.
|
Sorry, I mean util/StdioFile instead of CStdioFile. You can see the fopen() is actually encapsulated in a class called StdioFile. If we use fopen64() instead of fopen(), we should modify StdioFile instead. |
Hi nestal sync ./4g doesn't exist in server, uploading [PN2gr4http6UrlTagE] = https://docs.google.com/feeds/default/private/changes?start-index=129 |
@indian4646 Yes, you are right. I have just added the protocol/AuthAgent to refresh the token. I didn't check the expire time like you did, just refresh the token whenever we get a 401. Can you please take a look? If it doesn't work at your side, can you please modify protocol/AuthAgent to add whatever you need? You can also add things to protocol/OAuth2. I don't expect we need to touch other places for this. |
Hi
I have updated grive in my fork grive. I have checked uploading large file successfully and spend over 3600 second for refresh token.
https://github.com/indian4646/grive
1.I modified support more 2gb filesize,
2.Checking "exprie in" time for long-lived access token
The text was updated successfully, but these errors were encountered: