From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: rack-devel@googlegroups.com
Subject: Re: Why env.object_id is different in each middleware?
Date: Thu, 10 Dec 2009 00:15:17 +0100 [thread overview]
Message-ID: <200912100015.17445.ibc@aliax.net> (raw)
In-Reply-To: <200912092359.08240.ibc@aliax.net>
El Miércoles, 9 de Diciembre de 2009, Iñaki Baz Castillo escribió:
> Since env is a hash I cannot understand why its object_id changes. Any
> explanation for it?
> This explains that when I change env[XXX] into my final appplication
> MyApp.handle_request the change doesn't exist after calling
> resp = @app.call(env)
> in the first middleware.
If I add a env["LALA"] in the first middleware then it's visible for following
middlewares.
However if I add env["LOLO"] in the second middleware this is not visible for
first middleware after calling "@app.call(env)".
Is it the expected behavior?
Thanks.
--
Iñaki Baz Castillo <ibc@aliax.net>
next prev parent reply other threads:[~2009-12-09 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:59 Why env.object_id is different in each middleware? Iñaki Baz Castillo
2009-12-09 23:15 ` Iñaki Baz Castillo [this message]
2010-01-04 0:50 ` Tim Carey-Smith
2010-01-04 0:58 ` Iñaki Baz Castillo
2010-01-04 19:44 ` Iñaki Baz Castillo
2010-01-05 20:57 ` Ryan Tomayko
2010-01-05 23:47 ` Iñaki Baz Castillo
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=200912100015.17445.ibc@aliax.net \
--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).