From: Simon Rozet <simon@rozet.name>
To: rack-devel@googlegroups.com
Subject: Re: Rack as a client-side spec
Date: Thu, 2 Jul 2009 18:11:55 +0200 [thread overview]
Message-ID: <8878c9770907020911m87cab2br55fe91ce8b5c70e@mail.gmail.com> (raw)
In-Reply-To: <dba10c06-4e84-4ff9-9279-e207fb4d9b8f@37g2000yqp.googlegroups.com>
On Wed, Jul 1, 2009 at 8:00 PM, Bill Burcham<bill.burcham@gmail.com> wrote:
>
> This sounded like a great idea a few weeks ago. Now I've got a real
> use case: I'm in the process of implementing a little ZIP-code lookup
> service for a client (hits http://zip4.usps.com/zip4/welcome.jsp) and
> I'm wishing I had a (client-side) middleware for caching those
> responses.
>
Checkout cacheability which hacks RestClient to use Rack::Cache
http://github.com/cryx/cacheability
--
Simon Rozet <simon@rozet.name> http://atonie.org
next prev parent reply other threads:[~2009-07-02 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 4:16 Rack as a client-side spec Tim Carey-Smith
2009-05-05 6:48 ` Daniel N
2009-05-10 11:35 ` Christian Neukirchen
2009-05-10 14:10 ` Joshua Peek
2009-05-10 22:54 ` Daniel N
2009-07-01 18:00 ` Bill Burcham
2009-07-02 16:11 ` Simon Rozet [this message]
2009-07-02 19:41 ` Bill Burcham
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=8878c9770907020911m87cab2br55fe91ce8b5c70e@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).