From: "Chris St. John" <chris@stjohnstudios.com>
To: rack-devel@googlegroups.com
Subject: Re: using Memcached or Redis inside Rack? Wise?
Date: Sat, 2 Apr 2011 23:41:30 -0400 [thread overview]
Message-ID: <BANLkTikGikoUmJtssO7+4HstWRQ7SJMwZg@mail.gmail.com> (raw)
In-Reply-To: <6f165bc8-3999-49d7-b0b4-48dec3ebd134@o21g2000prh.googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
Sounds like a good plan to me. In this case, Rails is just a big rack app
with a lot of things you wouldn't be using.
On Apr 2, 2011 11:12 PM, "Ned" <rails.nerd@gmail.com> wrote:
> Hi
>
> I have a rails application that redirects based on information in a
> memcached or redis store
>
> It does this for every request
>
> I'd like to move that logic to Rack so I can keep it as low level as
> possible (Yes I realise Rails makes this very easy and it might be
> more appropriate... but this really is low level conditional logic)
>
> Thing is, I can't see any blogs from people using Memcached or Redis
> from inside Rack.
>
> Is it just not done?
[-- Attachment #2: Type: text/html, Size: 905 bytes --]
next prev parent reply other threads:[~2011-04-03 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 0:53 using Memcached or Redis inside Rack? Wise? Ned
2011-04-03 3:41 ` Chris St. John [this message]
2011-04-03 8:27 ` Armin Roehrl
2011-04-03 8:28 ` Julio Cesar Ody
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikGikoUmJtssO7+4HstWRQ7SJMwZg@mail.gmail.com \
--to=rack-devel@googlegroups.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 read-only IMAP folder(s) and NNTP newsgroup(s).