I'm using JRuby, outside Rails currently (although I know people found
it interesting to benefits from existing deployment infrastructures).
I use it mainly for:
- reliable job processing/pdf generation with Resque + Java CRM
interop (post:
If you'll never need to parse xml requests anywhere you could set the
relevant entry in ActionController::Base.param_parsers to nil
thanks for the hint - it the application grows, I'll definitely try that :)
cheers,
-- Thibaut
--
You received this message because you are subscribed to the
Bumping this up - anyone knows how to disable params parsing ?
-- Thibaut
On Nov 17, 12:27 pm, Thibaut Barrère thibaut.barr...@gmail.com
wrote:
Hi,
I'm writing a service that receives XML posted data. By default
action_controller/params_parser.rb seems to try to parse the whole
thing
Hi,
I'm writing a service that receives XML posted data. By default
action_controller/params_parser.rb seems to try to parse the whole
thing to translate that into the params hash.
Is there a simple way to disable this parsing so that I can just store
the data on the disk without any check to
Hi,
a project I've been building on the side:
http://www.learnivore.com
It's a screencasts aggregator - so far I've indexed the most well-
known ruby/rails screencasts publishers, including:
- pragprogs
- railscasts
- peepcode
- envycasts
- (more, and others are planned)
Suggestions
Great job
Glad you like it :)
RubyPulse has just been added to the mix: http://bit.ly/9LxNH
cheers,
-- Thibaut
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To post to this group,
Hello,
I'm looking for some compatibility matrix between specific versions of
Ruby (like 1.8.5, 1.8.6...) and specific versions of Rails (like
1.1.6, 1.2.2 etc).
I'm in a position where I'll have to upgrade Ruby (to 1.8.6 or 1.8.7)
for old Rails app (typically 1.1.6 and 1.2.2), and that kind of
Hi Rob,
Well, since I know that Rails 1.1.6 and 1.2.2 application will run
fine under Ruby 1.8.6 (and 1.8.5), I'll start you with that. There's
plenty of evidence that Ruby 1.8.7 is more of a prequel to 1.9 than an
upgrade to 1.8.6 so you'll have to collect your own evidence about
Hi Jodi,
avoid 1.8.7 if you're rails 2.2 -
I had a number of problems (today) -
thanks for sharing this - I'm very sorry for your issues.
Maybe having some kind of community integration server to cross test the
various builds would be useful.
Did anyone do this already ?
cheers
Thibaut
Hello John,
I was very excited when I saw this, but I can't get it to work on my
system -- though I admit to having no knowledge of multibyte
characters and I would guess my problem is either an environment
issue, or a change that is happening in Rails 2.3, but perhaps you
could point me in
Hey there,
I just released DiacriticsFu 1.0.2 that should work with Rails = 2.2
and $KCODE UTF8 (the default Rails setup).
It's still a hack but I hope it will work for you :)
cheers
Thibaut
--
http://blog.logeek.fr
http://evolvingworker.com
I investigated a bit more:
- with a blank Rails 2.0.5 app, works as expected
- with a blank Rails 2.2.2 app, doesn't work
So obviously the = Rails 2.2.2 fix (see new_escaper.rb) does not work properly.
I'll keep you posted.
cheers
-- Thibaut
, 1.4.4,
1.4.2.
=== examples ===
DiacriticsFu::escape(éphémère)
= ephemere
DiacriticsFu::escape(räksmörgås)
= raksmorgas
=== feedback ? ===
In case you meet any issue, drop a mail ([EMAIL PROTECTED]).
cheers,
Thibaut Barrère
--
http://blog.logeek.fr
http://evolvingworker.com
13 matches
Mail list logo
