similar to: Crash occurs where EventMachine.connect is

I''ve actually found a way to make EventMachine listen to events from a serial port, but only by using the pure Ruby version, using Guilliame Pierronnet''s Ruby/SerialPort library. It turned out to be simpler than I thought it would be: require ''serialport'' $eventmachine_library = :pure_ruby require ''eventmachine'' module EventMachine class

I''m using the current release branch from the repository (version_0) on freebsd 6.1 with ruby 1.8.4. This is the error that is generated when running the code below at the bottom of the message, plus a gdb bt. Sorry no debugging symbols built into ruby but maybe the bt will help anyways. terminate called after throwing an instance of ''std::runtime_error'' what():

Hi EM Gurus, I''m hoping someone can shed some light on the following... I''m using a 3rd party (legacy) server that can accept up to 8 simultaneous connections on one port. I''ve been able to make multiple connections to this server from within one call to EventMachine::run {...}. Specificaly, I can access each connection separately using: em_thread = Thread.new do

Hello, I have been looking at the Ruby/EventMachine. First let me say it look very good. Reactor model with no threads makes for fast reliable server, and I have read about marvelous Twisted framework for Python and am glad to see something similar for Ruby. I am writing network app with Ruby threads now and it very slow, and I try new Ruby 1.9 with native threads that make it much slower.

Francis, I read in the list archives back that a future EventMachine release will support epoll on Linux (i.e., it''s in the trunk). Better still, is there a possibility that EM will rely on libevent so that it will be architecture independent (i.e. epoll on Linux, kqueue on FreeBSD/Mac OS X, /dev/poll on Solaris)? This is how memcached is implemented, and it would be helpful to be able

Is getsockname (or its equivalent) available to an EM Connection object? I''d like to access the local port number in my client application. --Michael

I made a quick patch to em so it will try to read the key/cert from a file if it exists in the cwd, and if not use the hardcoded default. If I added a function in rubymain.cpp to set the location of the pem file, where in em would be the right place to set it? It should be in the same scope as start_tls I would think. I''m checking for the pem file in InitializeDefaultCredentials().

Hi everyone. Does anyone have any preferences or ideas for an interface for SSL certificates, both client-side and server-side? At present, the only interface is EventMachine::Connection#start_tls, which uses a built-in self-signed cert on the server side. On the cilent side, it accepts any well-formed cert (that is, it doesn''t check that the remote cert is signed by a trusted authority).

Hi All, I''m currently looking into doing a bit of evented network programming in ruby and i''m currently looking into packet, eventmachine and rev. The problem is that I need to be able to fork and start a new reactor within the forked child (it also should open a socket and write status information back to the main process). I have not been able to do this with EventMachine.

Guys, Just for fun, I tried to see (I know, a silly way to test it) how much overhead we have calling the C functions of the extensions. the benchmark script and the results: http://pastie.caboo.se/128646 The naive C extension: http://pastie.caboo.se/128647 I compared 1.8.6 (VC6 and mingw builds) against a fresh checkout of ruby trunk. What I understand from that is 1.9 is slower than 1.8

Sorry this is going to be a bit vague, but I''ve noticed something rather odd going on with EventMachine on Linux. I''ve written something uses EventMachine to proxy HTTP to other processes. On OS X, it works great, adding only about 20% extra latency into the connection when proxying versus connecting to the original backend process directly, so a 5ms connection might now take

My Rails application requires a very busy worker process running in the background at all times. I am launching this non-interactive process using script/runner. This process is very busy and is communicating with the MySQL server constantly. As I started putting some load on the system to test, I started running into performance issues. I have since discovered that Rails is only using 1

I''ve added experiments/core-model-2 to SVN. I think this is pretty clean and satisfactory. Jeff, please have a look and see if you like the placement of timeouts (which are currently unimplemented). Any event now has the possibility of a timeout. To get an application-level timeout, you''d just post an event with a timeout to a nil target. When the timeout expires, the errback

Hello all, I''ve been learning Ruby and playing with a chat server I built using GServer. After into an issue I found with GServer, that no one else seemed to notice (actually, similar to this question, GServer is hard to kill nicely, especially when you want to.), I found references to EventMachine, and rebuilt my server using it. I much prefer EventMachine''s model. The

Short question: is there way to tell EM to actually send data after send_data call? I''m building a file transferring app. I send Mashal.dump''ed metadata first, and then - the file contents (chunked). I found a silly bug: receive_data() gets marshalled metadata and the first chunk of the file in a single variable. Like that: c1.send_data("meta")

An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20071018/a54f2b61/attachment.html

I upgraded from 12.2 to 12.4 and found that my happy little eventmachine processes die with: terminate called after throwing an instance of ''std::runtime_error'' what(): call SetTlsParms before calling StartTls Here''s what I believe is the relevant snippet of my code, which calls start_tls() in the connection_completed() callback: connection =

Friends, I am writing an event system which has an interface on a web site which can create events. The creation of events opens up EventMachine::run and connects to the event server, and sends messages. The problem comes if this is run inside of say, event driven mongrel, where it will crash fatally, the same as: EventMachine::run { EventMachine::run { } } The only solution that

I am using eventmachine 0.8.1 on windows XP and am having very odd problems. This snippet of code gives the error that follows it. class EchoServer def receive_data data puts data send_data ">>>you sent: #{data}" if data =~ /quit/i puts "quitting" close_connection EventMachine::stop_event_loop end end end

Hi , I am writing a rake task to consume twitter stream API. The task contains the following code: consumer = OAuth::Consumer.new(CONSUMER_KEY, CONSUMER_SECRET, :site => ''http://twitter.com'') access_token = OAuth::AccessToken.new(consumer,ACCESS_TOKEN,ACCESS_TOKEN_SECRET) oauth_params = {:consumer => consumer, :token => access_token} EventMachine.run do # now,