NE_SET_REQUEST_(3) neon API reference NE_SET_REQUEST_(3)NAME
ne_set_request_body_buffer, ne_set_request_body_fd - include a message body with a request
SYNOPSIS
#include <ne_request.h>
void ne_set_request_body_buffer (ne_request *req, const char *buf, size_t count);
DESCRIPTION
The ne_set_request_body_buffer function specifies that a message body should be included with the body, which is stored in the count bytes
buffer buf.
SEE ALSO ne_request_create(3)AUTHOR
Joe Orton <neon@webdav.org>.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Availability | SUNWneon |
+--------------------+-----------------+
|Interface Stability | Volatile |
+--------------------+-----------------+
NOTES
Source for Neon is available on http://opensolaris.org.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Availability | SUNWneon |
+--------------------+-----------------+
|Interface Stability | Volatile |
+--------------------+-----------------+
NOTES
Source for Neon is available on http://opensolaris.org.
neon 0.25.5 20 January 2006 NE_SET_REQUEST_(3)
Check Out this Related Man Page
NE_SET_REQUEST_BODY_(3) neon API reference NE_SET_REQUEST_BODY_(3)NAME
ne_set_request_body_buffer, ne_set_request_body_fd, ne_set_request_body_fd64 - include a message body with a request
SYNOPSIS
#include <ne_request.h>
void ne_set_request_body_buffer(ne_request *req, const char *buf, size_t count);
int ne_set_request_body_fd(ne_request *req, int fd, off_t begin, off_t length);
DESCRIPTION
The ne_set_request_body_buffer function specifies that a message body should be included with the body, which is stored in the count bytes
buffer buf.
The ne_set_request_body_fd function can be used to include a message body with a request which is read from a file descriptor. The body is
read from the file descriptor fd, which must be a associated with a seekable file (not a pipe, socket, or FIFO). count bytes are read,
beginning at offset begin (hence, passing begin as zero means the body is read from the beginning of the file).
For all the above functions, the source of the request body must survive until the request has been dispatched; neither the memory buffer
passed to ne_set_request_body_buffer nor the file descriptor passed to ne_set_request_body_fd are copied internally.
SEE ALSO
ne_request_create
AUTHOR
Joe Orton <neon@lists.manyfish.co.uk>
Author.
COPYRIGHT neon 0.30.0 31 July 2013 NE_SET_REQUEST_BODY_(3)
i am looking forward to this one:
http://www.opensolaris.org/jive/message.jspa?messageID=11672#11672
i thought that the gentoo community would release the first opensolaris distri, but perhabs we will get a chance to try opensolaris within 1/2 hour installation and not 12 hours "gentoo-stage_1"... (2 Replies)
Hi all,
I have two virtual machines, one with Suse and another with opensolaris 2009.06.
The ldap server is in the Suse machine.
From my opensolaris, with command ldalist i can see the information about the ldap configuration, i mean, the dn: ou:....
if i type id <ldapuser> i can see the user... (0 Replies)