Displaying 20 results from an estimated 1000 matches similar to: "Status of EventMachine.fork"
2007 Feb 25
6
Crash occurs where EventMachine.connect is
Hi everyone,
If you subclass EventMachine::Connection and call it outside an
EventMachine::run
event loop, EventMachine crashes! Example:
class Put < EventMachine::Connection
include EventMachine::Deferrable
HOST="localhost"
PORT=8080
def self.request(data)
EventMachine.connect(HOST, PORT, self) {|c|
c.instance_eval { @data = data }
}
end
#
2007 May 24
4
Multiple EM connections on separate threads
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
2008 Jan 14
10
Using EventMachine to listen from non-network
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
2007 Nov 09
1
EventMachine::run - How can I ensure that this
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
2007 Nov 07
4
Gracefully stopping EventMachine?
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
2007 Dec 09
38
libevent
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.
2008 Jan 06
5
Having very odd problems with UDP.
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
2011 Sep 26
2
undefined method `options' for #<EventMachine::HttpClien
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,
2008 Aug 06
6
Event loop responsiveness + client
Hello, on the application that I''m working on, we are using Thin.
The server implements long polling and commands that alter its internal state.
Connecting to the long poll is a very fast operation, while updating
the state of the server is a relatively slow operation.
The long poll connection is held open until there is a change to be
sent to the connection.
Here is my current
2006 May 22
3
core-model-2
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
2008 Aug 22
6
EventMachine website down?
Hi all
Is the EventMachine website (www.rubyeventmachine.com) down? I can''t access
it from South Africa, and have tried using tor as well with no luck.
I''m kinda new to EventMachine, so I first have a lot of examples to work
through and reading to do before I start pestering the mailing list with
questions.
Thanks to everyone who partook in creating the library, so far
2008 Mar 18
1
Eventmachine utils
I''m working on StrokeDB* right now and put pieces of networking stuff
into a separate repository "Eventmachine utils". There are 3 useful
libs already: protocol chaining, messaging protocol and marshalled
messaging protocol. Check them out :-)
Overview:
http://gitorious.org/projects/eventmachine-utils
Files:
2008 Oct 23
3
ANN: EMDRb 0.1.0
I am pleased to announce the release of EMDRb version 0.1.0, a
rudimentary implementation of a distributed Ruby server based on
EventMachine. It''s available on Rubyforge at
http://rubyforge.org/projects/emdrb but I must admit that it has thus
far only been lightly tested and still a bit feature incomplete. The
server implementation can already do all of the basic stuff one expects
DRb
2009 Mar 12
1
Rspec and EventMachine
Hey Guys,
I am trying to create a app that makes use of EventMachine.
As I recently fell in love with Rspec, I was trying to use it with our
EM. However, I have no idea how to do this. Also, I want to remove
network connections from the tests (as I might not be connected when
running them), so I think I should mock them up, but again... I don''t
know how to do this!
Any tips?
Thanks
2007 Dec 14
21
Some silly benchs (was: 1.9)
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
2008 Feb 07
6
Buffer flushing
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")
2007 Dec 10
21
BackgrounDRb 1.0 pre-release available now
Hi Folks,
We are glad to announce shiny new release of BackgrounDRb, which will
soon become 1.0.
A quick summary of changes:
- BackgrounDRb is no londer DRb, its based on event driven network
programming library packet ( http://www.packet.googlecode.com ) .
- Since we moved to packet, many nasty thread issues, result hash
corruption issues are totally gone. Lots of work has went in
making
2005 Jun 24
9
new mysql gem
Hi everyone,
For those who have/had problems with Webrick not properly closing MySQL
connections, there is a new MySQL gem. (Actually the version was
released some time ago, just nobody took the time to make a gem)
So run "gem update" or just "gem install mysql" to update (not sure if
the latter also updates).
Special thanks to Tobias Luetke, who forwarded the gem to Chad
2007 Sep 14
3
epoll appears to break
The following program is a minor variant on the sample given in the README
with eventmachine-0.8.1. I am running under CentOS 4.5 (kernel
2.6.9-55.0.2.plus.c4) with a ruby-1.8.5 RPM from the CentOS testing
repository.
When I run it, I find that set_comm_inactivity_timeout doesn''t do anything.
That is, if I client opens a connection, it stays open indefinitely.
However, if I comment out
2008 Feb 01
6
epoll increasing latency big time
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