List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: RFE: .so filters
Date: Sat, 11 Jan 2014 03:37:19 +0100	[thread overview]
Message-ID: <CAHmME9p0cxVKAn=7R0oszY5LGkxxoo4KdW9ZttAvCVsL2LV8Jg@mail.gmail.com> (raw)
In-Reply-To: <52D05E80.4000800@xinu.at>

On Fri, Jan 10, 2014 at 9:56 PM, Florian Pritz <bluewind at xinu.at> wrote:
> Last but not least, it keeps the interface between "exec" and "lua"
> filters the same or at least rather similar. If you can call a lua
> script as if it was execed (setting argv) that would make the handler
> totally transparent, but faster.

The whole point of this thread has been avoiding forking off new
processes, or instantiating new situations for each use of the filter.
By doing a filter_open, filter_write, and filter_close, all in the
same process, we could benefit from lazy deallocation of filter
resources, and therefore keep one lua runtime and parsed script, for
the duration of several calls to opening and closing a filter.


  reply	other threads:[~2014-01-11  2:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 21:34 Jason
2014-01-09 22:29 ` mailings
2014-01-09 22:58 ` john
2014-01-10  1:41   ` Jason
2014-01-10  2:11     ` Jason
2014-01-10  4:26       ` Jason
2014-01-10  9:06       ` john
2014-01-10 15:57         ` Jason
2014-01-10 17:12           ` bluewind
2014-01-10 17:20             ` john
2014-01-10 17:43               ` mricon
2014-01-10 18:00                 ` Jason
2014-01-10 18:00               ` Jason
2014-01-10 17:57             ` Jason
2014-01-10 20:03               ` bluewind
2014-01-10 20:11                 ` john
2014-01-10 20:25                   ` bluewind
2014-01-10 20:36                     ` john
2014-01-10 20:56                       ` bluewind
2014-01-11  2:37                         ` Jason [this message]
2014-01-11  2:34                 ` Jason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9p0cxVKAn=7R0oszY5LGkxxoo4KdW9ZttAvCVsL2LV8Jg@mail.gmail.com' \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).