2 Unix SMB/CIFS implementation.
3 Infrastructure for async requests
4 Copyright (C) Volker Lendecke 2008
6 This program is free software; you can redistribute it and/or modify
7 it under the terms of the GNU General Public License as published by
8 the Free Software Foundation; either version 3 of the License, or
9 (at your option) any later version.
11 This program is distributed in the hope that it will be useful,
12 but WITHOUT ANY WARRANTY; without even the implied warranty of
13 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 GNU General Public License for more details.
16 You should have received a copy of the GNU General Public License
17 along with this program. If not, see <http://www.gnu.org/licenses/>.
20 #ifndef __ASYNC_REQ_H__
21 #define __ASYNC_REQ_H__
26 * An async request moves between the following 4 states:
29 enum async_req_state
{
31 * we are creating the request
35 * we are waiting the request to complete
37 ASYNC_REQ_IN_PROGRESS
,
39 * the request is finished
43 * an error has occured
49 * @brief An async request
51 * This represents an async request being processed by callbacks via an event
52 * context. A user can issue for example a write request to a socket, giving
53 * an implementation function the fd, the buffer and the number of bytes to
54 * transfer. The function issuing the request will immediately return without
55 * blocking most likely without having sent anything. The API user then fills
56 * in req->async.fn and req->async.priv, functions that are called when the
57 * request is finished.
59 * It is up to the user of the async request to talloc_free it after it has
60 * finished. This can happen while the completion function is called.
65 * @brief The external state - will be queried by the caller
67 * While the async request is being processed, state will remain in
68 * ASYNC_REQ_IN_PROGRESS. A request is finished if
69 * req->state>=ASYNC_REQ_DONE.
71 enum async_req_state state
;
74 * @brief Private pointer for the actual implementation
76 * The implementation doing the work for the async request needs a
77 * current state like for example a fd event. The user of an async
78 * request should not touch this.
83 * @brief Print yourself, for debugging purposes
85 * Async requests are opaque data structures. The implementation of an
86 * async request can define a custom function to print more debug
89 char *(*print
)(TALLOC_CTX
*mem_ctx
, struct async_req
*);
92 * @brief status code when finished
94 * This status can be queried in the async completion function. It
95 * will be set to NT_STATUS_OK when everything went fine.
100 * @brief The event context we are using
102 * The event context that this async request works on.
104 struct event_context
*event_ctx
;
107 * @brief What to do on completion
109 * This is used for the user of an async request, fn is called when
110 * the request completes, either successfully or with an error.
114 * @brief Completion function
115 * Completion function, to be filled by the API user
117 void (*fn
)(struct async_req
*);
119 * @brief Private data for the completion function
125 struct async_req
*async_req_new(TALLOC_CTX
*mem_ctx
, struct event_context
*ev
);
127 char *async_req_print(TALLOC_CTX
*mem_ctx
, struct async_req
*req
);
129 void async_req_done(struct async_req
*req
);
131 void async_req_error(struct async_req
*req
, NTSTATUS status
);
133 bool async_post_status(struct async_req
*req
, NTSTATUS status
);
135 bool async_req_nomem(const void *p
, struct async_req
*req
);