[Rails] current status of concurrency: rails2.3/ruby1.9/thin

2009-05-10 Thread buddycat
hi all, i just got back from railsconf and forgot to ask a question. what is the current status of handling concurrent requests? i am migrating to rails2.3/ruby1.9 on thin and am confused about how many thins i need and whether i can serve up multiple concurrent requests to them. in front i use n

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-13 Thread buddycat
also, my particular case is with asp content; but i am sure that the problem can be reproduced with any web stack or even a static text file with these characters. On Apr 13, 6:52 pm, buddycat wrote: > so i use lib/asp.rb module to get legacy asp content from internal > win2k/iis5/asp (c

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-13 Thread buddycat
well but now need to do so with the former. imho. thanks...gg On Apr 13, 5:05 am, Conrad Taylor wrote: > 2009/4/13 buddycat > > > > > > > hector, > > > further update: > > > i was able to set both my internal and external encoding thanks to > > hong

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-13 Thread buddycat
at i started with. so...guess i am back to doing explicit encoding like you suggested or going back to iconv. all in all i have to say that ruby1.9 and rails2.3 and encoding and irb and compiling your own ruby and... are still very rough. ...gg On Apr 13, 12:40 am, buddycat wrote: > ok. found

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-12 Thread buddycat
bothering to see what version of ruby you are running. this fixes my immediate problem so thanks. am going to grep RUBY_PLATFORM to see if that can just be set somewhere in rails as that seems to be referenced before searching for system location of irb. ...gg On Apr 12, 8:27 pm, buddycat wrote

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-12 Thread buddycat
ternal_encoding in a transparent way. > I recommend you read this blog: > > http://blog.grayproductions.net/articles/ruby_19s_three_default_encod... > > Rails doesn't remove the Encoding class is available in the console. > I think your console for some reason is using ruby 1.8. > > O

[Rails] Re: invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-12 Thread buddycat
ternal_encoding in a transparent way. > I recommend you read this blog: > > http://blog.grayproductions.net/articles/ruby_19s_three_default_encod... > > Rails doesn't remove the Encoding class is available in the console. > I think your console for some reason is using ruby 1.8. > > O

[Rails] invalid byte sequence utf-8 OR best option to sanitize content brought in with net::http? single non-utf character causes rails to crash

2009-04-12 Thread buddycat
hi all, platform: debian lenny, ruby1.91.p0, passenger/apache-multithread, rails2.3 in vendor/postres and sql server via odbc. all current gems. i have legacy asp content on win2k servers that i wrap in rails controllers. this all worked great with ruby1.8, but now that we are dealing with encod

[Rails] Re: rails2.3/ruby1.9: invalid byte sequence in utf-8 with blank?

2009-04-11 Thread buddycat
coding methods exposed as they do in irb? On Apr 10, 6:24 pm, buddycat wrote: > thanks conrad, > > debian lenny > apache2-mpm-worker > dbd-odbc (0.2.4) > dbi (0.4.1) > deprecated (2.0.1) > fastthread (1.0.7) > json (1.1.4) > passenger (2.1.3) > pg (0.8.0)

[Rails] Re: rails2.3/ruby1.9: invalid byte sequence in utf-8 with blank?

2009-04-10 Thread buddycat
ncoding # rescue #raise "#{self.class} #{self.encoding.name} #{self.valid_encoding?} # {self}" # end end class Numeric #:nodoc: def blank? false end end On Apr 10, 6:04 pm, Conrad Taylor wrote: > On Fri, Apr 10, 2009 at 2:35 PM, buddycat wrote: > > > as an upda

[Rails] Re: rails2.3/ruby1.9: invalid byte sequence in utf-8 with blank?

2009-04-10 Thread buddycat
On Apr 10, 5:00 pm, buddycat wrote: > hi all, > > anyone seen this controller argument error: > > invalid byte sequence in utf-8 > > ror/vendor/rails/activesupport/lib/active_support/core_ext/blank.rb: > 50:in `=~' > ror/vendor/rails/activesupport/lib/active_su

[Rails] rails2.3/ruby1.9: invalid byte sequence in utf-8 with blank?

2009-04-10 Thread buddycat
hi all, anyone seen this controller argument error: invalid byte sequence in utf-8 ror/vendor/rails/activesupport/lib/active_support/core_ext/blank.rb: 50:in `=~' ror/vendor/rails/activesupport/lib/active_support/core_ext/blank.rb: 50:in `!~' ror/vendor/rails/activesupport/lib/active_support/co

[Rails] rails assumption about getting new thread on each request

2009-04-07 Thread buddycat
hi all, i am wondering if there is consensus around whether it is an assumption of the rails core that each request will be served by a new, clean thread? i ask because i am using Thread.current hash and while mongrel seems to handle each request with a new thread and so Thread.current is clean,