From 4a5d55fc8627866e5c72db7efeb20d869ad7b669 Mon Sep 17 00:00:00 2001 From: "arseny.kapoulkine@gmail.com" Date: Tue, 27 Mar 2012 03:28:41 +0000 Subject: docs: Small fix git-svn-id: http://pugixml.googlecode.com/svn/trunk@886 99668b35-9821-0410-8761-19e4c4f06640 --- docs/manual.qbk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual.qbk b/docs/manual.qbk index e71da8d..bdaa0a7 100644 --- a/docs/manual.qbk +++ b/docs/manual.qbk @@ -1260,7 +1260,7 @@ All of the above saving functions are implemented in terms of writer interface. void xml_document::save(xml_writer& writer, const char_t* indent = "\t", unsigned int flags = format_default, xml_encoding encoding = encoding_auto) const; -In order to output the document via some custom transport, for example sockets, you should create an object which implements `xml_writer_file` interface and pass it to `save` function. `xml_writer_file::write` function is called with a buffer as an input, where `data` points to buffer start, and `size` is equal to the buffer size in bytes. `write` implementation must write the buffer to the transport; it can not save the passed buffer pointer, as the buffer contents will change after `write` returns. The buffer contains the chunk of document data in the desired encoding. +In order to output the document via some custom transport, for example sockets, you should create an object which implements `xml_writer` interface and pass it to `save` function. `xml_writer::write` function is called with a buffer as an input, where `data` points to buffer start, and `size` is equal to the buffer size in bytes. `write` implementation must write the buffer to the transport; it can not save the passed buffer pointer, as the buffer contents will change after `write` returns. The buffer contains the chunk of document data in the desired encoding. `write` function is called with relatively large blocks (size is usually several kilobytes, except for the first block with BOM, which is output only if [link format_write_bom] is set, and last block, which may be small), so there is often no need for additional buffering in the implementation. -- cgit v1.2.3