Artifactspublic-v0

curl

master
ply4 git calls250 ms288 KiB2 cachedprotocol v2
66 lines1.5 KiBRaw

NAME

CURLOPT_WRITEDATA - pointer passed to the write callback

SYNOPSIS

c
#include <curl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_WRITEDATA, void *pointer);

DESCRIPTION

A data pointer to pass to the write callback. If you use the CURLOPT_WRITEFUNCTION(3) option, this is the pointer you get in that callback's fourth and last argument. If you do not use a write callback, you must make pointer a 'FILE ' (cast to 'void *') as libcurl passes this to *fwrite(3) when writing data.

The internal CURLOPT_WRITEFUNCTION(3) writes the data to the FILE * given with this option, or to stdout if this option has not been set.

If you are using libcurl as a Windows DLL, you must also use CURLOPT_WRITEFUNCTION(3) if you set this option or you might experience crashes.

DEFAULT

stdout

%PROTOCOLS%

EXAMPLE

A common technique is to use the write callback to store the incoming data into a dynamically growing allocated buffer, and then this CURLOPT_WRITEDATA(3) is used to point to a struct or the buffer to store data in. Like in the getinmemory example: https://curl.se/libcurl/c/getinmemory.html

HISTORY

This option was formerly known as CURLOPT_FILE, the name CURLOPT_WRITEDATA(3) was added in 7.9.7.

%AVAILABILITY%

RETURN VALUE

This returns CURLE_OK.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: CURLOPT_WRITEDATA
5Section: 3
6Source: libcurl
7See-also:
8 - CURLOPT_HEADERDATA (3)
9 - CURLOPT_READDATA (3)
10 - CURLOPT_WRITEFUNCTION (3)
11Protocol:
12 - All
13Added-in: 7.9.7
14---
16# NAME
18CURLOPT_WRITEDATA - pointer passed to the write callback
20# SYNOPSIS
22~~~c
23#include <curl/curl.h>
25CURLcode curl_easy_setopt(CURL *handle, CURLOPT_WRITEDATA, void *pointer);
26~~~
28# DESCRIPTION
30A data *pointer* to pass to the write callback. If you use the
31CURLOPT_WRITEFUNCTION(3) option, this is the pointer you get in that
32callback's fourth and last argument. If you do not use a write callback, you
33must make *pointer* a 'FILE *' (cast to 'void *') as libcurl passes this
34to *fwrite(3)* when writing data.
36The internal CURLOPT_WRITEFUNCTION(3) writes the data to the FILE *
37given with this option, or to stdout if this option has not been set.
39If you are using libcurl as a Windows DLL, you must also use
40CURLOPT_WRITEFUNCTION(3) if you set this option or you might experience
41crashes.
43# DEFAULT
45stdout
47# %PROTOCOLS%
49# EXAMPLE
51A common technique is to use the write callback to store the incoming data
52into a dynamically growing allocated buffer, and then this
53CURLOPT_WRITEDATA(3) is used to point to a struct or the buffer to store data
54in. Like in the *getinmemory* example:
55https://curl.se/libcurl/c/getinmemory.html
57# HISTORY
59This option was formerly known as CURLOPT_FILE, the name CURLOPT_WRITEDATA(3)
60was added in 7.9.7.
62# %AVAILABILITY%
64# RETURN VALUE
66This returns CURLE_OK.
Diagnostics4 git calls · 250 ms
CallStatusSizeTime0250 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
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 · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
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 · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=245
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
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
fetch200898 B245 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=898
git.response.cache=MISS
git.response.duration_ms=245
git.fetch.wants=f6c6a2eeb9f1e7286295ab207f7451726afb95de
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=898
git.pkt.payload.max=877
git.sideband.band1.bytes=876
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
a5e363ea3fa9b23b
Request
52bf6274…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format