Skip to content

Download ParseFile content to file instead of memory #53

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

Conversation

wangmengyan95
Copy link
Contributor

No description provided.

@wangmengyan95 wangmengyan95 force-pushed the wangmengyan.t8120706_download_ParseFile_content_to_file_instead_of_memory branch 2 times, most recently from 00e0b3a to 6d20873 Compare August 25, 2015 02:13
@wangmengyan95 wangmengyan95 added this to the 1.10.2 milestone Aug 25, 2015

public ParseAWSRequest(Method method, String url) {
// The temp file is used to save the ParseFile content when we fetch it from server
private File tempFile;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: final

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kk

}

@Override
protected Task<byte[]> onResponseAsync(ParseHttpResponse response,
protected Task<Void> onResponseAsync(ParseHttpResponse response,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably do the operations in this method on ParseExecutors.io() since we're doing disk i/o now or else we'd be on ParseRequest.NETWORK_EXECUTOR by default.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping ^

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops, forgot this point, sorry.

@grantland
Copy link
Contributor

It seems like we're going to have to have a proper solution for managing our cache. I'll create a new issue for it.

@grantland
Copy link
Contributor

Created #98.

Might be worthwhile to move staging into it's own directory so that we can keep cache size separate of cache size. In addition it would allow us to merge this without needing to depend on #98 since the cache manager would clear staging files without a one-off condition.

@wangmengyan95 wangmengyan95 removed their assignment Sep 2, 2015
@grantland
Copy link
Contributor

Can you rebase master? It looks like there are conflicts with master.

@wangmengyan95 wangmengyan95 force-pushed the wangmengyan.t8120706_download_ParseFile_content_to_file_instead_of_memory branch from efe3382 to dd591a9 Compare September 3, 2015 21:49
@grantland grantland assigned wangmengyan95 and unassigned grantland Sep 3, 2015
@grantland
Copy link
Contributor

LGTM

wangmengyan95 added a commit that referenced this pull request Sep 3, 2015
…ad_ParseFile_content_to_file_instead_of_memory

Download ParseFile content to file instead of memory
@wangmengyan95 wangmengyan95 merged commit 063ce1b into master Sep 3, 2015
@wangmengyan95 wangmengyan95 deleted the wangmengyan.t8120706_download_ParseFile_content_to_file_instead_of_memory branch September 3, 2015 23:59
@facebook-github-bot
Copy link

@wangmengyan95 updated the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants