rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Matt Todd <chiology@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack-compatible server issues
Date: Fri, 4 Dec 2009 22:42:52 -0800	[thread overview]
Message-ID: <2a8d4a710912042242i49e7385x17630050274e2ea9@mail.gmail.com> (raw)
In-Reply-To: <683a886f0912041804p29185909j9abcb55c555e0f89@mail.gmail.com>

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

>
> http://gist.github.com/249506
>
> If I pass just the lambda, my server runs fine, but if I pass the
> whole builder-created app (any combination of middleware), I get one
> of the middleware classes returned from the #call(env) method.
>

In that code, you're calling a use after the lambda... that lambda is
essentially disappearing. You should return that lambda.

If it's any value, I've never liked using the builder personally.

Matt



-- 
Matt Todd
Highgroove Studios
www.highgroove.com
cell: 404-314-2612
blog: maraby.org

Scout - Web Monitoring and Reporting Software
www.scoutapp.com

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

  reply	other threads:[~2009-12-05  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05  2:04 Rack-compatible server issues Kevin Williams
2009-12-05  6:42 ` Matt Todd [this message]
2009-12-05 15:51   ` Kevin Williams
2009-12-05 20:49     ` Iñaki Baz Castillo
2009-12-05 22:55       ` Scytrin dai Kinthra
2009-12-05  6:43 ` Michael Fellinger
2009-12-05 16:00   ` Kevin Williams
2009-12-05 17:05     ` Kevin Williams

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=2a8d4a710912042242i49e7385x17630050274e2ea9@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).