From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 border1.nntp.dca.giganews.com!nntp.giganews.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: RFC: markdown to HTML library
Date: Mon, 20 Jan 2014 09:34:13 +0100
Organization: cbb software GmbH
Message-ID: <pqag9zb1o7el$.gh29g30boydn$.dlg@40tude.net>
References: <slrnldok7s.1lme.lithiumcat@sigil.instinctive.eu>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: I5Na6+WsEzT8WoegI0VZTA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: number.nntp.dca.giganews.com comp.lang.ada:184482
Date: 2014-01-20T09:34:13+01:00
List-Id: <comp.lang.ada>

On Sun, 19 Jan 2014 22:26:04 +0000 (UTC), Natasha Kerensikova wrote:

> Features request are welcome too, though I can't tell for now when I
> will manage to look into them. Currently reStructuedText front-end and
> and fully-configurable ODT back-end are on my radar.
> 
> I can get into the details of how it works internally, but I won't bore
> you with it if it's not necessary.

There are many different requirements depending on the usage, I guess.

Now to the way my HTTP server works. The content is generated and not
stored in a file, though the latter is possible of course. That is because
the server is intended for embedded platforms, which may have no disk space
or it could be undesirable to write anything on the disk.

For the same reason the content should be fed to a state machine in pieces
that fit into the outgoing buffer. This is because the server does not
allocate memory dynamically by itself and because it is driven by the
buffer-ready event.

So the library for generating content should be able to work in the
corresponding manner. E.g. upon a GET request the content must be prepared
and its sending only initiated. Then another time on another context chunks
of the content are sequentially requested as they are sent away. I.e. the
thing must maintain internal state and not spilling all guts in one shot.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de