Roxen.git/
server/
etc/
modules/
Roxen.pmod
Branch:
Tag:
Non-build tags
All tags
No tags
2001-03-12
2001-03-12 20:46:42 by Johan Sundström <oyasumi@gmail.com>
4d5c3cb452aa7c2ef9074b673f86cda4bc2f078c (
17
lines) (+
12
/-
5
)
[
Show
|
Annotate
]
Branch:
5.2
Upgraded docs for Roxen.http_pipe_in_progress() somewhat.
Rev: server/etc/modules/Roxen.pmod:1.74
1:
// This is a roxen pike module. Copyright © 1999 - 2000, Roxen IS. //
-
// $Id: Roxen.pmod,v 1.
73
2001/03/12
15
:46:
23
mast
Exp $
+
// $Id: Roxen.pmod,v 1.
74
2001/03/12
20
:46:
42
jhs
Exp $
#include <roxen.h> #include <config.h>
136:
]); }
+
//! Returns a response mapping indicating that the module or script
+
//! will take over the rest of the handling of the request. This
+
//! aborts the request chain and leaves you in control for as long as
+
//! you wish.
+
//!
+
//! Typically, you'll want to return the control again by sending a
+
//! new result mapping to @[RequestID.send_result()], but should you
+
//! want to glue together request headers and close the socket on your
+
//! own, you are free to do so. The method @[RequestID.connection()]
+
//! gives you the Stdio.File object for the current client connection.
mapping http_pipe_in_progress()
-
//! Return a result mapping that indicates that the request file
-
//! should be kept open, but no result should be sent. Another result
-
//! mapping can be sent later on with the send_result member
-
//! function of the protocol object, if it is available.
+
{ HTTP_WERR("Pipe in progress"); return ([ "file":-1, "pipe":1, ]);