Eventmachine talk - Nov 2007 - Eventmachine-talk Digest, Vol 19, Issue 10

> This is a pretty interesting question, actually. I haven''t hit
> busy-loop problems with #next_tick in this kind of application because
> I usually schedule the next data to send on #next_tick only if the
> outbound buffer of a connection is above a certain amount (like a
> megabyte, for example). Since the kernel will be eating up the
> outbound data in the background, some work is generally being done all
> the time.
>
> Are you doing this a different way?
File streamer just polls next_tick to each tick check if the outbound
queue length is below a threshold.  I tried a similar approach and
discovered the inefficiency in such a mechanism.
Ideally would be something like
self.when_outbound_queue_goes_below_x_run_this(200000, proc { # do stuff
}
)
or what not.


> I tried to build eventmachine on mingw in a couple of different
configurations, but came up against compilation errors attached at the bottom of
this e-mail.
>
> Does eventmachine support mingw at this time?
> OpenSSL 0.9.7c is in my path and includes, so shouldn''t it have
been found?
>
> Any help would be gratefully recieved.
>
> Regards,
>
Looks to me like it links to g++ libs (?).  This is interesting as
ruby MRI uses only gcc to compile.  Making it compatible with that
might make it more cross platform compatible (like we care--99%
probably use win32 and linux/osx so..using c++ is probably ok).
Just a thought.
Take care!
-Roger