Artifactspublic-v0

curl

master
ply4 git calls181 ms288 KiB2 cachedprotocol v2
67 lines2.4 KiBRaw

ABI - Application Binary Interface

"ABI" describes the low-level interface between an application program and a library. Calling conventions, function arguments, return values, struct sizes/defines and more.

Wikipedia has a longer description

Upgrades

A libcurl upgrade does not break the ABI or change established and documented behavior. Your application can remain using libcurl like before, only with fewer bugs and possibly with added new features.

Version Numbers

In libcurl land, you cannot tell by the libcurl version number if that libcurl is binary compatible or not with another libcurl version. As a rule, we do not break the ABI so you can always upgrade to a later version without any loss or change in functionality.

SONAME Bumps

Whenever there are changes done to the library that causes an ABI breakage, that may require your application to get attention or possibly be changed to adhere to new things, we bump the SONAME. Then the library gets a different output name and thus can in fact be installed in parallel with an older installed lib (on most systems). Thus, old applications built against the previous ABI version remains working and using the older lib, while newer applications build and use the newer one.

During the first seven years of libcurl releases, there have only been four ABI breakages.

We are determined to bump the SONAME as rarely as possible. Ideally, we never do it again.

Downgrades

Going to an older libcurl version from one you are currently using can be a tricky thing. Mostly we add features and options to newer libcurls as that does not break ABI or hamper existing applications. This has the implication that going backwards may get you in a situation where you pick a libcurl that does not support the options your application needs. Or possibly you even downgrade so far so you cross an ABI break border and thus a different SONAME, and then your application may need to adapt to the modified ABI.

History

The previous major library SONAME number bumps (breaking backwards compatibility) happened the following times:

0 - libcurl 7.1, August 2000

1 - libcurl 7.5 December 2000

2 - libcurl 7.7 March 2001

3 - libcurl 7.12.0 June 2004

4 - libcurl 7.16.0 October 2006

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# ABI - Application Binary Interface
9"ABI" describes the low-level interface between an application program and a
10library. Calling conventions, function arguments, return values, struct
11sizes/defines and more.
13[Wikipedia has a longer description](https://en.wikipedia.org/wiki/Application_binary_interface)
15## Upgrades
17A libcurl upgrade does not break the ABI or change established and documented
18behavior. Your application can remain using libcurl like before, only with
19fewer bugs and possibly with added new features.
21## Version Numbers
23In libcurl land, you cannot tell by the libcurl version number if that
24libcurl is binary compatible or not with another libcurl version. As a rule,
25we do not break the ABI so you can *always* upgrade to a later version without
26any loss or change in functionality.
28## SONAME Bumps
30Whenever there are changes done to the library that causes an ABI breakage,
31that may require your application to get attention or possibly be changed to
32adhere to new things, we bump the SONAME. Then the library gets a different
33output name and thus can in fact be installed in parallel with an older
34installed lib (on most systems). Thus, old applications built against the
35previous ABI version remains working and using the older lib, while newer
36applications build and use the newer one.
38During the first seven years of libcurl releases, there have only been four
39ABI breakages.
41We are determined to bump the SONAME as rarely as possible. Ideally, we never
42do it again.
44## Downgrades
46Going to an older libcurl version from one you are currently using can be a
47tricky thing. Mostly we add features and options to newer libcurls as that
48does not break ABI or hamper existing applications. This has the implication
49that going backwards may get you in a situation where you pick a libcurl that
50does not support the options your application needs. Or possibly you even
51downgrade so far so you cross an ABI break border and thus a different
52SONAME, and then your application may need to adapt to the modified ABI.
54## History
56The previous major library SONAME number bumps (breaking backwards
57compatibility) happened the following times:
590 - libcurl 7.1, August 2000
611 - libcurl 7.5 December 2000
632 - libcurl 7.7 March 2001
653 - libcurl 7.12.0 June 2004
674 - libcurl 7.16.0 October 2006
Diagnostics4 git calls · 181 ms
CallStatusSizeTime0181 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=176
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
fetch2001.2 KiB176 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1260
git.response.cache=MISS
git.response.duration_ms=176
git.fetch.wants=9cd2ad801b19e811800c2ad7d95ebc655a7bd629
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=1260
git.pkt.payload.max=1239
git.sideband.band1.bytes=1238
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
a5e328adcff64628
Request
1c273c5e…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format