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
e20f3ecd
Commit
e20f3ecd
authored
15 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
clarify what a modern version of libcurl means
parent
c83f7ede
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/curl_multi_socket_action.3
+6
-6
6 additions, 6 deletions
docs/libcurl/curl_multi_socket_action.3
with
6 additions
and
6 deletions
docs/libcurl/curl_multi_socket_action.3
+
6
−
6
View file @
e20f3ecd
...
...
@@ -95,13 +95,13 @@ for more actions on libcurl's sockets. You don't have to do it immediately,
but the return code means that libcurl may have more data available to return
or that there may be more data to send off before it is "satisfied".
In modern libcurls
, \fICURLM_CALL_MULTI_PERFORM\fP or
\fICURLM_CALL_MULTI_SOKCET\fP
should
not be
returned and no application needs
to care about them.
In modern libcurls
(from around 7.19.0 or later),
\fICURLM_CALL_MULTI_PERFORM\fP or
\fICURLM_CALL_MULTI_SOKCET\fP
will
not be
returned and no application needs
to care about them.
NOTE that the return code is for the whole multi stack.
Problems still might have
occurred on individual transfers even when one of
these functions
return OK.
NOTE that the return code
from this function
is for the whole multi stack.
Problems still might have
occurred on individual transfers even when one of
these functions
return OK.
.SH "TYPICAL USAGE"
1. Create a multi handle
...
...
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