pull: Add queuing into the higher level logic
Working on the libcurl backend, I didn't want to reimplement another queue. I think the queue logic is really better done at the high level, since the fetcher knows how we want to prioritize metadata over content, etc. Adding another queue here is duplication, but things will look nicer when we can actually delete the libsoup one in the next commit. Closes: #654 Approved by: jlebon
This commit is contained in:
1 parent
3d38f03e4f
commit
c18628ecb8
2 files changed
+198
-42
No files matched your search
@@ -32,6 +32,9 @@ G_BEGIN_DECLS
|
||||
#define _OSTREE_SUMMARY_CACHE_DIR "summaries"
|
||||
#define _OSTREE_CACHE_DIR "cache"
|
||||
|
||||
#define _OSTREE_MAX_OUTSTANDING_FETCHER_REQUESTS 8
|
||||
#define _OSTREE_MAX_OUTSTANDING_DELTAPART_REQUESTS 2
|
||||
|
||||
typedef enum {
|
||||
OSTREE_REPO_TEST_ERROR_PRE_COMMIT = (1 << 0)
|
||||
} OstreeRepoTestErrorFlags;
|
||||
|
||||
Reference in new issue
Block a user