search for: stable_1

...9;s happen with receiving a message from an external program in your case. I got round it by calling the external program via Win32API on Windows, instead of ruby''s own system/backticks. There''s some code that encapsulates this here: http://weft-qda.rubyforge.org/svn/branches/stable_1-0/weft-qda/lib/weft/filters/win32backtick.rb hth alex

FYI. -- - Brian Gupta http://opensolaris.org/os/project/nycosug/

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002

Hi all, There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want fixed before they release it. If it''s ok with people I''d like to fix that, revert (at least for now) the proxy response change, and tag that as 1.1.2 and release it. Anything wrong with this plan? Evan -- Evan Weaver Cloudburst, LLC

Hi Alex, Hi Weft-Users! I am looking for a tool for doing a qualitative analysis of mailing-list data. This means I have a *lot* of individual documents (the typical case: around 500-5000 emails), belonging to the same "super-document" (a mailing list). I have looked at several tools and I like that Weft is public domain and written in Ruby, so I want to figure out whether it

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be