Difference between revisions of "Ns adp stream"
Jump to navigation
Jump to search
(imported from WiKit id 874) |
|||
| Line 15: | Line 15: | ||
: This command turns on "streaming mode" of ADP output, where output is immediately sent instead of queued up in an output buffer. All data in the current ADP output buffer is flushed and written to the client and any subsequent data will be immediately written as well. | : This command turns on "streaming mode" of ADP output, where output is immediately sent instead of queued up in an output buffer. All data in the current ADP output buffer is flushed and written to the client and any subsequent data will be immediately written as well. | ||
| − | : | + | : In AOLserver 4.5, this is equivalent to an [[ns_adp_flush]] followed by an [[ns_adp_ctl]] bufsize 0. |
| − | : Streaming does not work well through proxies. The user may be forced to wait on a blank screen until your script finishes its work and closes the connection. Therefore, streaming is likely to yield a very poor user interface experience and should be avoided except when actually necessary. | + | : Streaming does not work well through proxies. The user may be forced to wait on a blank screen until your script finishes its work and closes the connection. Therefore, streaming is likely to yield a very poor user interface experience and should be avoided except when actually necessary. - THIS IS SOMEWHAT DATED ADVICE |
'''SEE ALSO''' | '''SEE ALSO''' | ||
Latest revision as of 02:14, 18 June 2010
Man page: http://aolserver.com/docs/tcl/ns_adp_stream.html
NAME
- ns_adp_stream - Begin streaming of ADP output
SYNOPSIS
- ns_adp_stream
DESCRIPTION
- This command turns on "streaming mode" of ADP output, where output is immediately sent instead of queued up in an output buffer. All data in the current ADP output buffer is flushed and written to the client and any subsequent data will be immediately written as well.
- In AOLserver 4.5, this is equivalent to an ns_adp_flush followed by an ns_adp_ctl bufsize 0.
- Streaming does not work well through proxies. The user may be forced to wait on a blank screen until your script finishes its work and closes the connection. Therefore, streaming is likely to yield a very poor user interface experience and should be avoided except when actually necessary. - THIS IS SOMEWHAT DATED ADVICE
SEE ALSO
- ns_adp_abort, ns_adp_append, ns_adp_argc, ns_adp_argv, ns_adp_bind_args, ns_adp_break, ns_adp_debug, ns_adp_debuginit, ns_adp_dir, ns_adp_dump, ns_adp_eval, ns_adp_exception, ns_adp_include, ns_adp_mime, ns_adp_mimetype, ns_adp_parse, ns_adp_puts, ns_adp_registeradp, ns_adp_registerproc, ns_adp_registertag, ns_adp_return, ns_adp_safeeval, ns_adp_stats, ns_adp_tell, ns_adp_trunc
