Artifactspublic-v0

curl

master
ply4 git calls163 ms288 KiB2 cachedprotocol v2
65 lines1.9 KiBRaw

NAME

libcurl-share - how to use the share interface

DESCRIPTION

This is an overview on how to use the libcurl share interface in your C programs. There are specific man pages for each function mentioned in here.

All functions in the share interface are prefixed with curl_share.

OBJECTIVES

The share interface was added to enable sharing of data between curl handles.

ONE SET OF DATA - MANY TRANSFERS

You can have multiple easy handles share data between them. Have them update and use the same cookie database, DNS cache, TLS session cache and/or connection cache. This way, each single transfer takes advantage from data updates made by the other transfer(s).

SHARE OBJECT

You create a shared object with curl_share_init(3). It returns a handle for a newly created one.

You tell the shared object what data you want it to share by using curl_share_setopt(3).

Since you can use this share from multiple threads, and libcurl has no internal thread synchronization, you must provide mutex callbacks if you are using this multi-threaded. You set lock and unlock functions with curl_share_setopt(3) too.

Then, you make an easy handle to use this share, you set the CURLOPT_SHARE(3) option with curl_easy_setopt(3), and pass in share handle. You can make any number of easy handles share the same share handle.

To make an easy handle stop using that particular share, you set CURLOPT_SHARE(3) to NULL for that easy handle. To make a handle stop sharing a particular data, you can CURLSHOPT_UNSHARE(3) it.

When you are done using the share, make sure that no easy handle is still using it, and call curl_share_cleanup(3) on the handle.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: libcurl-share
5Section: 3
6Source: libcurl
7See-also:
8 - curl_share_cleanup (3)
9 - curl_share_init (3)
10 - curl_share_setopt (3)
11 - libcurl-easy (3)
12 - libcurl-errors (3)
13 - libcurl-multi (3)
14Protocol:
15 - All
16Added-in: n/a
17---
19# NAME
21libcurl-share - how to use the share interface
23# DESCRIPTION
25This is an overview on how to use the libcurl share interface in your C
26programs. There are specific man pages for each function mentioned in
27here.
29All functions in the share interface are prefixed with curl_share.
31# OBJECTIVES
33The share interface was added to enable sharing of data between curl handles.
35# ONE SET OF DATA - MANY TRANSFERS
37You can have multiple easy handles share data between them. Have them update
38and use the **same** cookie database, DNS cache, TLS session cache and/or
39connection cache. This way, each single transfer takes advantage from data
40updates made by the other transfer(s).
42# SHARE OBJECT
44You create a shared object with curl_share_init(3). It returns a handle
45for a newly created one.
47You tell the shared object what data you want it to share by using
48curl_share_setopt(3).
50Since you can use this share from multiple threads, and libcurl has no
51internal thread synchronization, you must provide mutex callbacks if you are
52using this multi-threaded. You set lock and unlock functions with
53curl_share_setopt(3) too.
55Then, you make an easy handle to use this share, you set the
56CURLOPT_SHARE(3) option with curl_easy_setopt(3), and pass in
57share handle. You can make any number of easy handles share the same share
58handle.
60To make an easy handle stop using that particular share, you set
61CURLOPT_SHARE(3) to NULL for that easy handle. To make a handle stop
62sharing a particular data, you can CURLSHOPT_UNSHARE(3) it.
64When you are done using the share, make sure that no easy handle is still using
65it, and call curl_share_cleanup(3) on the handle.
Diagnostics4 git calls · 163 ms
CallStatusSizeTime0163 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=158
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001016 B158 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1016
git.response.cache=MISS
git.response.duration_ms=158
git.fetch.wants=040059313d6b6836f71520a7d19bb5ccb471afce
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1016
git.pkt.payload.max=995
git.sideband.band1.bytes=994
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e354f4d9a7994c
Request
a32b4192…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format