From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Add redis-db module to upstream?
Date: Wed, 7 Jun 2017 15:10:06 -0700 [thread overview]
Message-ID: <170607151006.ZM17896@torch.brasslantern.com> (raw)
In-Reply-To: <16324.1496827747@thecus.kiddle.eu>
On Jun 7, 11:29am, Oliver Kiddle wrote:
}
} Certrainly we want to take care that the hiredis dependency isn't making
} a zsh build more complicated. Perhaps the module could be disabled by
} default.
I believe this can be taken care of by configure, in the same way that
gdbm and pcre are left uncompiled if configure can't find them.
} I'd also agree with the points made by Bart such as unifying
} ztie, perhaps with a generic typeset option: typeset -o file=...
I think a separate builtin like ztie is the right way to go here,
rather than further overloading typeset. We need a way to select
the module (ztie -d ...) and to specify external objects (ztie -f
and possibly other options if the notion of a "file" doesn't match
the usage).
} As for use, I've never actually got around to trying the gdbm module.
} What is it mostly good for? Very large variables or sharing variables?
Mostly it's for providing a shell-level interface to anything you would
store in a simple attibute-value database. Specifically to zsh it can
be used to share state among shells (for example IF we could rely on it
gdbm woule be a much better file store for _store_cache/_retrieve_cache
than the current mechanism of serializing arrays).
If I understand redis's built-in clustering mechanism correctly, it
could be used to share state among shells on different hosts as well.
next prev parent reply other threads:[~2017-06-07 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 3:24 Sebastian Gniazdowski
2017-06-03 17:09 ` Bart Schaefer
2017-06-03 19:35 ` Daniel Shahaf
2017-06-04 5:57 ` Sebastian Gniazdowski
2017-06-04 6:23 ` Sebastian Gniazdowski
2017-06-06 2:28 ` Eric Cook
2017-06-07 9:29 ` Oliver Kiddle
2017-06-07 11:08 ` Sebastian Gniazdowski
2017-06-07 13:04 ` Daniel Shahaf
2017-06-07 22:10 ` Bart Schaefer [this message]
2017-06-04 8:35 ` Sebastian Gniazdowski
2017-06-08 4:01 Sebastian Gniazdowski
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=170607151006.ZM17896@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).