9.8
;ˆ¾Ê
0ÉÀÎ
=ˆ¾Ê
0ÉÀÎ
?Ñ
358ÐÀÎ f ?
403 Forbidden
Forbidden
You don't have permission to access this resource.
Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.
% Aˆl—Ým_Jµ2ÛB‚ € ¸ËwmLZ7ÿË
„e§ gÊÁÏ ?÷ A/*
* Copyright (c) 2000-2007 Niels Provos
* Copyright (c) 2007-2012 Niels Provos and Nick Mathewson
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. The name of the author may not be used to endorse or promote products
* derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
#ifndef EVENT2_BUFFEREVENT_H_INCLUDED_
#define EVENT2_BUFFEREVENT_H_INCLUDED_
/**
@file event2/bufferevent.h
Functions for buffering data for network sending or receiving. Bufferevents
are higher level than evbuffers: each has an underlying evbuffer for reading
and one for writing, and callbacks that are invoked under certain
circumstances.
A bufferevent provides input and output buffers that get filled and
drained automatically. The user of a bufferevent no longer deals
directly with the I/O, but instead is reading from input and writing
to output buffers.
Once initialized, the bufferevent structure can be used repeatedly
with bufferevent_enable() and bufferevent_disable().
When reading is enabled, the bufferevent will try to read from the
file descriptor onto its input buffer, and call the read callback.
When writing is enabled, the bufferevent will try to write data onto its
file descriptor when the output buffer has enough data, and call the write
callback when the output buffer is sufficiently drained.
Bufferevents come in several flavors, including:
- Socket-based bufferevents
- A bufferevent that reads and writes data onto a network
socket. Created with bufferevent_socket_new().
- Paired bufferevents
- A pair of bufferevents that send and receive data to one
another without touching the network. Created with
bufferevent_pair_new().
- Filtering bufferevents
- A bufferevent that transforms data, and sends or receives it
over another underlying bufferevent. Created with
bufferevent_filter_new().
- SSL-backed bufferevents
- A bufferevent that uses the openssl library to send and
receive data over an encrypted connection. Created with
bufferevent_openssl_socket_new() or
bufferevent_openssl_filter_new().
*/
#include
#ifdef __cplusplus
extern "C" {
#endif
#include
#ifdef EV