rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Daniel N <has.sox@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack as a client-side spec
Date: Mon, 11 May 2009 08:54:07 +1000	[thread overview]
Message-ID: <2fff50390905101554u4feea72akaea9315f371cf820@mail.gmail.com> (raw)
In-Reply-To: <1c5622660905100710k104fc87fpf185716ac7c39dfd@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

Looks like Tim forgot to link his lib

http://github.com/halorgium/rack-client/tree/master

Cheers


On Mon, May 11, 2009 at 12:10 AM, Joshua Peek <josh@joshpeek.com> wrote:

>
> This sounds pretty cool.
>
> I don't think anything needs to be done SPEC wise. We just need some
> good tools here. Something to build raw http requests from an env
> hash, and something to parse http requests (servers do this now).
> Maybe a general tool like Rack::Utils.build_request(env) and
> Rack::Utils.parse_request(io) would be a useful addition.
>
> On Sun, May 10, 2009 at 6:35 AM, Christian Neukirchen
> <chneukirchen@gmail.com> wrote:
> >
> > Tim Carey-Smith <g@spork.in> writes:
> >
> >> Does this sound like a good idea? It means we can leverage the power
> >> of middleware on the client-side too.
> >
> > It's awesome!
> >
> > --
> > Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org
> >
>
>
>
> --
> Joshua Peek
>

[-- Attachment #2: Type: text/html, Size: 1669 bytes --]

  reply	other threads:[~2009-05-10 22:55 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 [this message]
2009-07-01 18:00       ` Bill Burcham
2009-07-02 16:11         ` Simon Rozet
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=2fff50390905101554u4feea72akaea9315f371cf820@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).