Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
4ebf4f6e
Commit
4ebf4f6e
authored
21 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
better mentioning of other functions to create proper hrefs in the web
version
parent
4d86593f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/libcurl/libcurl-share.3
+10
-10
10 additions, 10 deletions
docs/libcurl/libcurl-share.3
with
10 additions
and
10 deletions
docs/libcurl/libcurl-share.3
+
10
−
10
View file @
4ebf4f6e
...
...
@@ -20,27 +20,27 @@ You can have multiple easy handles share data between them. Have them update
and use the \fBsame\fP cookie database or DNS cache! This way, each single
transfer will take advantage from data updates made by the other transfer(s).
.SH "SHARE OBJECT"
You create a shared object with \fIcurl_share_init()\fP. It returns a handle
You create a shared object with \fIcurl_share_init(
3
)\fP. It returns a handle
for a newly created one.
You tell the shared object what data you want it to share by using
\fIcurl_share_setopt()\fP. Currently you can only share DNS and/or COOKIE
\fIcurl_share_setopt(
3
)\fP. Currently you can only share DNS and/or COOKIE
data.
Since you can use this share from multiple threads, and libcurl has no
internal thread synchronization, you must provide mutex callbacks if you're
using this multi-threaded. You set lock and unlock functions with
\fIcurl_share_setopt()\fP too.
\fIcurl_share_setopt(
3
)\fP too.
Then, you make an easy handle to use this share, you set the
CURLOPT_SHARE
option with \fIcurl_easy_setopt\fP, and pass in share
handle. You can make any
number of easy handles share the same share handle.
Then, you make an easy handle to use this share, you set the
\fICURLOPT_SHARE\fP
option with \fIcurl_easy_setopt
(3)
\fP, 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
to NULL for that easy handle. To make a handle stop
sharing a particular data,
you can CURLSHOPT_UNSHARE it.
To make an easy handle stop using that particular share, you set
\fICURLOPT_SHARE\fP
to NULL for that easy handle. To make a handle stop
sharing a particular data,
you can
\fI
CURLSHOPT_UNSHARE
\fP
it.
When you're done using the share, make sure that no easy handle is still using
it, and call \fIcurl_share_cleanup()\fP on the handle.
it, and call \fIcurl_share_cleanup(
3
)\fP on the handle.
.SH "SEE ALSO"
.BR curl_share_init "(3), " curl_share_setopt "(3), " curl_share_cleanup "(3)"
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment