Hmmmmm, cookies problem still not solved.
Now they are set, but for a strange reason, I can't read them. In the
middle of an action, I get:
p cookies.inspect
=> {"_session_id"=>"BAh7BzoMY3NyZl9pZCIlMjQ0MzM2MzYyODkzOWJj...",
"lang"=>"en"}
p cookies["_session_id"]
=> nil
p cookies["lang"]
=> nil
p cookies.keys
=> {"_session_id", "lang"}
p cookies.values
=> {"BAh7BzoMY3NyZl9pZCIlMjQ0MzM2MzYyODkzOWJj...", "en"}
p cookies[cookies.keys.first]
=> nil
And I've noticed a couple more things:
1. I wasn't able to start thin with it:
rackup -p 3000 -s thin
Unless I put in my environment (or a require somewhere):
config.gem 'thin'
Are you planning to handle those things by default? =)
2. Mongrel starts really slowly and without messages. On the other
hand, Webrick and Thin (after the first step) work like a charm! =)
On Jun 3, 4:05 am, Joshua Peek <[EMAIL PROTECTED]> wrote:
> Alright I think I got it fixed.
>
> http://github.com/rails/rails/commit/92050f6c6f586b2a73aeb61da4f41b98...
>
> Can someone test out the streaming stuff?
>
> On Jun 2, 9:53 am, José Valim <[EMAIL PROTECTED]> wrote:
>
> > I wasn't able to make sessions work here.
> > I was using :cookie_store, then I've changed to :memory_store and
> > nothing.
>
> > I've cleaned my cookies and then I saw that my application wasn't able
> > to story the session_key in cookies.
>
> > Any known hack to make it work?
>
> > On Jun 2, 4:09 pm, Rodrigo Kochenburger <[EMAIL PROTECTED]> wrote:
>
> > > That is great news.
> > > I'll also try to experiment with it.
>
> > > Thanks for adding it ;)
>
> > > On Jun 2, 8:37 am, José Valim <[EMAIL PROTECTED]> wrote:
>
> > > > Nice! I will take a look into it this afternoon and run some tests!
>
> > > > On Jun 1, 11:20 pm, Joshua Peek <[EMAIL PROTECTED]> wrote:
>
> > > > > The Rack processor, that Erza and I have been working on, is finally
> > > > > in trunk. This change will not effect your app. In fact, all of the
> > > > > server commands will still run CGI. All the CGI internals will stick
> > > > > around until this migration is complete. In order to test out the new
> > > > > rack goodies, you'll need to setup a config file for the rackup
> > > > > command.
>
> > > > > Please help test this rack stuff out. Once we're pretty confident in
> > > > > the processor, we'll start switching over script/server, mongrel_rails
> > > > > and all those server commands to use Rack by default.
>
> > > > > Here is a rackup config to get you
> > > > > started.http://pastie.caboo.se/206893
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
