From: Bill Burcham <bill.burcham@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack as a client-side spec
Date: Thu, 2 Jul 2009 12:41:06 -0700 [thread overview]
Message-ID: <bb99361a0907021241l7ef0cb29va62bf86f44d133b4@mail.gmail.com> (raw)
In-Reply-To: <8878c9770907020911m87cab2br55fe91ce8b5c70e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
Ooh cool thanks Simon. I have a little (familiar) problem now: the service
I'm hitting is form-based. So I have to POST to it. That breaks the rules of
course since POST is supposed to create resources and as such is not
cache-able according to HTTP.
So this sort of caching doesn't fit neatly into REST orthodoxy. An expedient
answer of course is just to fork cacheability. Is there a better answer?
[-- Attachment #2: Type: text/html, Size: 437 bytes --]
prev parent reply other threads:[~2009-07-02 19:41 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
2009-07-02 19:41 ` Bill Burcham [this message]
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=bb99361a0907021241l7ef0cb29va62bf86f44d133b4@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).