[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: feature request, saved state resumement

From: ikhxcsz7y xmbott
Subject: Re: feature request, saved state resumement
Date: Sat, 6 Nov 2021 08:33:58 +0100

you, in some far time, wont get around implenting ( such simpleness )

the nearer it is to 'specify overall coding practices' into drafts, the
nearer you must by specs

if this posix doesnt specify right extendments in 20 years, it was really
definatly the wrong horse to put *any thing* on it

for me, thats no problem, im just a computer keyboard user in a world full
of wrong anti software only, .. cant do anything about it
.. besides <such> emails

On Sat, Nov 6, 2021, 08:24 Alex fxmbsw7 Ratchev <> wrote:

> say, in a big complex app ( not one script but resources split ), say if my
> bashhttpd was any big and complete to http 1 or 2, there would be at least
> one state to be saved and resumed, for resources and speed, that is after
> it loaded and either then or before reading the request, that is when all
> base functions and stuff is loaded ( parsed say, loaded long list of
> functions, either with in between code to run, prolly, or just the long
> loading of <yea ita prepared now..> )
> the <is prepared now> state is usually the desired enterpoint of running
> some code project, by the coders
> i have it a bit impleted, i hash a long find -printf to text, and if that
> exists simply cat the code
> .. but im at still this point i write that, there is high mergin between
> is-ready, not at my httpd but this as-is-of-stuff

reply via email to

[Prev in Thread] Current Thread [Next in Thread]