On Wed, 21 Nov 2007 12:45:01 -0800
Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>
> Yeah I ported evented mongrel to run on packet> it does run and is
> faster than threaded mongrel, not quite as fast as event machine
> evented mongrel.
>
> The one problem is that the first reque
On Nov 21, 2007 3:08 PM, Jason Young <[EMAIL PROTECTED]> wrote:
> HOORAY! HOORAY! HOORAY!
>
> Jason
:)
Please let me know if you find any issues.
Thanks,
~Wayne
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailma
Yeah I ported evented mongrel to run on packet> it does run and is
faster than threaded mongrel, not quite as fast as event machine
evented mongrel.
The one problem is that the first request after server boot hangs but
then all requests after that are fine. I will continue s
HOORAY! HOORAY! HOORAY!
Jason
On Nov 20, 2007, at 10:47 PM, Wayne E. Seguin wrote:
Steve,
I just committed a change set to trunk that prepends Time.now.httpdate
to most output strings.
I am refactoring the logging to be more uniform and will be setting it
up to log using the common logfile
Hi Mongrels,
Anyone used Packet? http://rubyforge.org/projects/packet
It's a pure-Ruby (I think) evented framework. It might offer a nice
way forward for 1.9's system threads, JRuby, and Windows, all at once.
Mongrel's green thread queue doesn't have a lot of life left in it.
Evan
--
Evan Wea
It already has Mongrel support!
~/gems/packet-0.1.0/lib/packet_mongrel.rb
Evan
On Nov 21, 2007 10:19 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Hi Mongrels,
>
> Anyone used Packet? http://rubyforge.org/projects/packet
>
> It's a pure-Ruby (I think) evented framework. It might offer a nice
> wa
Incidentally that "no method error 'w'" is already fixed in trunk; we
need some more test coverage of an unrelated change before we can make
a release though.
Evan
On Nov 21, 2007 7:33 AM, Oliver Schneider <[EMAIL PROTECTED]> wrote:
> Hi,
> thank you for your help.
> I didn't patch anything.
>
>
Hi,
thank you for your help.
I didn't patch anything.
There isn't much load on the server. Its something about a call to a label,
every 20 or 30 seconds. Threre is enough Ram, that's not the problem. Cpu
power is enough. I simply don't know why it stops working.
In an older Mongrel version the er
I would have expected you to be getting the following on load:
c:/ruby/lib/ruby/gems/1.8/gems/daemons-1.0.9/lib/daemons/daemonize.rb:103:in
`fork': fork() function is unimplemented on this machine (NotImplementedError)
The "-d" is not actually supported on Windows, thus the warning:
> ** WARNING:
Hi,
I am using a railsapp to call an external app and print some barcode-labels.
My problem is, after a while there seems to be a timeout. Then I need to
stop the Mongrel-Server and restart it.
Below you can see the error message, when i stop the server.
Has somebody seen this before?
Greetings,
On Nov 21, 2007 4:56 AM, James Tucker <[EMAIL PROTECTED]> wrote:
> Luis Lavena wrote:
> > On Nov 21, 2007 3:18 AM, James Tucker <[EMAIL PROTECTED]> wrote:
> >> Yeah this is an unfortunate bug with the way that 'bin' files are setup on
> >> windows. In particular, you can't call exec on a text file
On Nov 21, 2007 4:49 AM, Csaba Okrona <[EMAIL PROTECTED]> wrote:
> Thank you both, Geoffrey and cdr for your help.
> I didn't know it was threaded on win32 by default :)
>
> Then I don't really get why there's so big performance difference bw/ a unix
> backed mongrel
> and a win32 one...
>
The cur
12 matches
Mail list logo
