MattHulse-eventmachine 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/.gitignore +14 -0
- data/README +82 -0
- data/Rakefile +279 -0
- data/docs/COPYING +60 -0
- data/docs/ChangeLog +211 -0
- data/docs/DEFERRABLES +133 -0
- data/docs/EPOLL +141 -0
- data/docs/GNU +281 -0
- data/docs/INSTALL +13 -0
- data/docs/KEYBOARD +38 -0
- data/docs/LEGAL +25 -0
- data/docs/LIGHTWEIGHT_CONCURRENCY +70 -0
- data/docs/PURE_RUBY +75 -0
- data/docs/RELEASE_NOTES +94 -0
- data/docs/SMTP +2 -0
- data/docs/SPAWNED_PROCESSES +89 -0
- data/docs/TODO +8 -0
- data/eventmachine.gemspec +41 -0
- data/examples/ex_channel.rb +43 -0
- data/examples/ex_queue.rb +2 -0
- data/examples/helper.rb +2 -0
- data/ext/binder.cpp +125 -0
- data/ext/binder.h +46 -0
- data/ext/cmain.cpp +821 -0
- data/ext/cplusplus.cpp +202 -0
- data/ext/ed.cpp +1868 -0
- data/ext/ed.h +416 -0
- data/ext/em.cpp +2270 -0
- data/ext/em.h +228 -0
- data/ext/emwin.cpp +300 -0
- data/ext/emwin.h +94 -0
- data/ext/epoll.cpp +26 -0
- data/ext/epoll.h +25 -0
- data/ext/eventmachine.h +122 -0
- data/ext/eventmachine_cpp.h +96 -0
- data/ext/extconf.rb +138 -0
- data/ext/fastfilereader/extconf.rb +84 -0
- data/ext/fastfilereader/mapper.cpp +214 -0
- data/ext/fastfilereader/mapper.h +59 -0
- data/ext/fastfilereader/rubymain.cpp +127 -0
- data/ext/files.cpp +94 -0
- data/ext/files.h +65 -0
- data/ext/kb.cpp +81 -0
- data/ext/page.cpp +107 -0
- data/ext/page.h +51 -0
- data/ext/pipe.cpp +349 -0
- data/ext/project.h +147 -0
- data/ext/rubymain.cpp +1152 -0
- data/ext/sigs.cpp +89 -0
- data/ext/sigs.h +32 -0
- data/ext/ssl.cpp +460 -0
- data/ext/ssl.h +94 -0
- data/java/.classpath +8 -0
- data/java/.project +17 -0
- data/java/src/com/rubyeventmachine/Application.java +192 -0
- data/java/src/com/rubyeventmachine/Connection.java +74 -0
- data/java/src/com/rubyeventmachine/ConnectionFactory.java +37 -0
- data/java/src/com/rubyeventmachine/DefaultConnectionFactory.java +46 -0
- data/java/src/com/rubyeventmachine/EmReactor.java +557 -0
- data/java/src/com/rubyeventmachine/EmReactorException.java +40 -0
- data/java/src/com/rubyeventmachine/EventableChannel.java +69 -0
- data/java/src/com/rubyeventmachine/EventableDatagramChannel.java +189 -0
- data/java/src/com/rubyeventmachine/EventableSocketChannel.java +364 -0
- data/java/src/com/rubyeventmachine/PeriodicTimer.java +38 -0
- data/java/src/com/rubyeventmachine/Timer.java +54 -0
- data/java/src/com/rubyeventmachine/tests/ApplicationTest.java +108 -0
- data/java/src/com/rubyeventmachine/tests/ConnectTest.java +146 -0
- data/java/src/com/rubyeventmachine/tests/EMTest.java +80 -0
- data/java/src/com/rubyeventmachine/tests/TestDatagrams.java +53 -0
- data/java/src/com/rubyeventmachine/tests/TestServers.java +74 -0
- data/java/src/com/rubyeventmachine/tests/TestTimers.java +89 -0
- data/lib/em/buftok.rb +138 -0
- data/lib/em/callback.rb +26 -0
- data/lib/em/channel.rb +57 -0
- data/lib/em/connection.rb +564 -0
- data/lib/em/deferrable.rb +187 -0
- data/lib/em/file_watch.rb +54 -0
- data/lib/em/future.rb +61 -0
- data/lib/em/messages.rb +66 -0
- data/lib/em/process_watch.rb +44 -0
- data/lib/em/processes.rb +119 -0
- data/lib/em/protocols.rb +35 -0
- data/lib/em/protocols/header_and_content.rb +138 -0
- data/lib/em/protocols/httpclient.rb +263 -0
- data/lib/em/protocols/httpclient2.rb +582 -0
- data/lib/em/protocols/line_and_text.rb +126 -0
- data/lib/em/protocols/linetext2.rb +160 -0
- data/lib/em/protocols/memcache.rb +323 -0
- data/lib/em/protocols/object_protocol.rb +45 -0
- data/lib/em/protocols/postgres3.rb +247 -0
- data/lib/em/protocols/saslauth.rb +175 -0
- data/lib/em/protocols/smtpclient.rb +350 -0
- data/lib/em/protocols/smtpserver.rb +547 -0
- data/lib/em/protocols/stomp.rb +200 -0
- data/lib/em/protocols/tcptest.rb +53 -0
- data/lib/em/queue.rb +61 -0
- data/lib/em/spawnable.rb +85 -0
- data/lib/em/streamer.rb +130 -0
- data/lib/em/timers.rb +55 -0
- data/lib/em/version.rb +3 -0
- data/lib/eventmachine.rb +1698 -0
- data/lib/evma.rb +32 -0
- data/lib/evma/callback.rb +32 -0
- data/lib/evma/container.rb +75 -0
- data/lib/evma/factory.rb +77 -0
- data/lib/evma/protocol.rb +87 -0
- data/lib/evma/reactor.rb +48 -0
- data/lib/jeventmachine.rb +246 -0
- data/lib/pr_eventmachine.rb +1022 -0
- data/setup.rb +1585 -0
- data/tasks/cpp.rake +77 -0
- data/tasks/project.rake +79 -0
- data/tasks/tests.rake +193 -0
- data/tests/client.crt +31 -0
- data/tests/client.key +51 -0
- data/tests/test_attach.rb +126 -0
- data/tests/test_basic.rb +284 -0
- data/tests/test_channel.rb +63 -0
- data/tests/test_connection_count.rb +35 -0
- data/tests/test_defer.rb +47 -0
- data/tests/test_epoll.rb +160 -0
- data/tests/test_error_handler.rb +35 -0
- data/tests/test_errors.rb +82 -0
- data/tests/test_exc.rb +55 -0
- data/tests/test_file_watch.rb +49 -0
- data/tests/test_futures.rb +198 -0
- data/tests/test_handler_check.rb +37 -0
- data/tests/test_hc.rb +218 -0
- data/tests/test_httpclient.rb +218 -0
- data/tests/test_httpclient2.rb +153 -0
- data/tests/test_inactivity_timeout.rb +50 -0
- data/tests/test_kb.rb +60 -0
- data/tests/test_ltp.rb +182 -0
- data/tests/test_ltp2.rb +317 -0
- data/tests/test_next_tick.rb +133 -0
- data/tests/test_object_protocol.rb +37 -0
- data/tests/test_process_watch.rb +48 -0
- data/tests/test_processes.rb +128 -0
- data/tests/test_proxy_connection.rb +92 -0
- data/tests/test_pure.rb +125 -0
- data/tests/test_queue.rb +44 -0
- data/tests/test_running.rb +42 -0
- data/tests/test_sasl.rb +72 -0
- data/tests/test_send_file.rb +242 -0
- data/tests/test_servers.rb +76 -0
- data/tests/test_smtpclient.rb +83 -0
- data/tests/test_smtpserver.rb +85 -0
- data/tests/test_spawn.rb +322 -0
- data/tests/test_ssl_args.rb +68 -0
- data/tests/test_ssl_methods.rb +50 -0
- data/tests/test_ssl_verify.rb +82 -0
- data/tests/test_timers.rb +162 -0
- data/tests/test_ud.rb +36 -0
- data/tests/testem.rb +31 -0
- data/web/whatis +7 -0
- metadata +223 -0
@@ -0,0 +1,187 @@
|
|
1
|
+
#--
|
2
|
+
#
|
3
|
+
# Author:: Francis Cianfrocca (gmail: blackhedd)
|
4
|
+
# Homepage:: http://rubyeventmachine.com
|
5
|
+
# Date:: 16 Jul 2006
|
6
|
+
#
|
7
|
+
# See EventMachine and EventMachine::Connection for documentation and
|
8
|
+
# usage examples.
|
9
|
+
#
|
10
|
+
#----------------------------------------------------------------------------
|
11
|
+
#
|
12
|
+
# Copyright (C) 2006-07 by Francis Cianfrocca. All Rights Reserved.
|
13
|
+
# Gmail: blackhedd
|
14
|
+
#
|
15
|
+
# This program is free software; you can redistribute it and/or modify
|
16
|
+
# it under the terms of either: 1) the GNU General Public License
|
17
|
+
# as published by the Free Software Foundation; either version 2 of the
|
18
|
+
# License, or (at your option) any later version; or 2) Ruby's License.
|
19
|
+
#
|
20
|
+
# See the file COPYING for complete licensing information.
|
21
|
+
#
|
22
|
+
#---------------------------------------------------------------------------
|
23
|
+
#
|
24
|
+
#
|
25
|
+
|
26
|
+
module EventMachine
|
27
|
+
module Deferrable
|
28
|
+
|
29
|
+
# Specify a block to be executed if and when the Deferrable object receives
|
30
|
+
# a status of :succeeded. See #set_deferred_status for more information.
|
31
|
+
#
|
32
|
+
# Calling this method on a Deferrable object whose status is not yet known
|
33
|
+
# will cause the callback block to be stored on an internal list.
|
34
|
+
# If you call this method on a Deferrable whose status is :succeeded, the
|
35
|
+
# block will be executed immediately, receiving the parameters given to the
|
36
|
+
# prior #set_deferred_status call.
|
37
|
+
#
|
38
|
+
#--
|
39
|
+
# If there is no status, add a callback to an internal list.
|
40
|
+
# If status is succeeded, execute the callback immediately.
|
41
|
+
# If status is failed, do nothing.
|
42
|
+
#
|
43
|
+
def callback &block
|
44
|
+
return unless block
|
45
|
+
if @deferred_status == :succeeded
|
46
|
+
block.call(*@deferred_args)
|
47
|
+
elsif @deferred_status != :failed
|
48
|
+
@callbacks ||= []
|
49
|
+
@callbacks.unshift block # << block
|
50
|
+
end
|
51
|
+
end
|
52
|
+
|
53
|
+
# Specify a block to be executed if and when the Deferrable object receives
|
54
|
+
# a status of :failed. See #set_deferred_status for more information.
|
55
|
+
#--
|
56
|
+
# If there is no status, add an errback to an internal list.
|
57
|
+
# If status is failed, execute the errback immediately.
|
58
|
+
# If status is succeeded, do nothing.
|
59
|
+
#
|
60
|
+
def errback &block
|
61
|
+
return unless block
|
62
|
+
if @deferred_status == :failed
|
63
|
+
block.call(*@deferred_args)
|
64
|
+
elsif @deferred_status != :succeeded
|
65
|
+
@errbacks ||= []
|
66
|
+
@errbacks.unshift block # << block
|
67
|
+
end
|
68
|
+
end
|
69
|
+
|
70
|
+
# Sets the "disposition" (status) of the Deferrable object. See also the large set of
|
71
|
+
# sugarings for this method.
|
72
|
+
# Note that if you call this method without arguments,
|
73
|
+
# no arguments will be passed to the callback/errback.
|
74
|
+
# If the user has coded these with arguments, then the
|
75
|
+
# user code will throw an argument exception.
|
76
|
+
# Implementors of deferrable classes <b>must</b>
|
77
|
+
# document the arguments they will supply to user callbacks.
|
78
|
+
#
|
79
|
+
# OBSERVE SOMETHING VERY SPECIAL here: you may call this method even
|
80
|
+
# on the INSIDE of a callback. This is very useful when a previously-registered
|
81
|
+
# callback wants to change the parameters that will be passed to subsequently-registered
|
82
|
+
# ones.
|
83
|
+
#
|
84
|
+
# You may give either :succeeded or :failed as the status argument.
|
85
|
+
#
|
86
|
+
# If you pass :succeeded, then all of the blocks passed to the object using the #callback
|
87
|
+
# method (if any) will be executed BEFORE the #set_deferred_status method returns. All of the blocks
|
88
|
+
# passed to the object using #errback will be discarded.
|
89
|
+
#
|
90
|
+
# If you pass :failed, then all of the blocks passed to the object using the #errback
|
91
|
+
# method (if any) will be executed BEFORE the #set_deferred_status method returns. All of the blocks
|
92
|
+
# passed to the object using # callback will be discarded.
|
93
|
+
#
|
94
|
+
# If you pass any arguments to #set_deferred_status in addition to the status argument,
|
95
|
+
# they will be passed as arguments to any callbacks or errbacks that are executed.
|
96
|
+
# It's your responsibility to ensure that the argument lists specified in your callbacks and
|
97
|
+
# errbacks match the arguments given in calls to #set_deferred_status, otherwise Ruby will raise
|
98
|
+
# an ArgumentError.
|
99
|
+
#
|
100
|
+
#--
|
101
|
+
# We're shifting callbacks off and discarding them as we execute them.
|
102
|
+
# This is valid because by definition callbacks are executed no more than
|
103
|
+
# once. It also has the magic effect of permitting recursive calls, which
|
104
|
+
# means that a callback can call #set_deferred_status and change the parameters
|
105
|
+
# that will be sent to subsequent callbacks down the chain.
|
106
|
+
#
|
107
|
+
# Changed @callbacks and @errbacks from push/shift to unshift/pop, per suggestion
|
108
|
+
# by Kirk Haines, to work around the memory leak bug that still exists in many Ruby
|
109
|
+
# versions.
|
110
|
+
#
|
111
|
+
# Changed 15Sep07: after processing callbacks or errbacks, CLEAR the other set of
|
112
|
+
# handlers. This gets us a little closer to the behavior of Twisted's "deferred,"
|
113
|
+
# which only allows status to be set once. Prior to making this change, it was possible
|
114
|
+
# to "succeed" a Deferrable (triggering its callbacks), and then immediately "fail" it,
|
115
|
+
# triggering its errbacks! That is clearly undesirable, but it's just as undesirable
|
116
|
+
# to raise an exception is status is set more than once on a Deferrable. The latter
|
117
|
+
# behavior would invalidate the idiom of resetting arguments by setting status from
|
118
|
+
# within a callback or errback, but more seriously it would cause spurious errors
|
119
|
+
# if a Deferrable was timed out and then an attempt was made to succeed it. See the
|
120
|
+
# comments under the new method #timeout.
|
121
|
+
#
|
122
|
+
def set_deferred_status status, *args
|
123
|
+
cancel_timeout
|
124
|
+
@deferred_status = status
|
125
|
+
@deferred_args = args
|
126
|
+
case @deferred_status
|
127
|
+
when :succeeded
|
128
|
+
if @callbacks
|
129
|
+
while cb = @callbacks.pop
|
130
|
+
cb.call(*@deferred_args)
|
131
|
+
end
|
132
|
+
end
|
133
|
+
@errbacks.clear if @errbacks
|
134
|
+
when :failed
|
135
|
+
if @errbacks
|
136
|
+
while eb = @errbacks.pop
|
137
|
+
eb.call(*@deferred_args)
|
138
|
+
end
|
139
|
+
end
|
140
|
+
@callbacks.clear if @callbacks
|
141
|
+
end
|
142
|
+
end
|
143
|
+
|
144
|
+
|
145
|
+
# Setting a timeout on a Deferrable causes it to go into the failed state after
|
146
|
+
# the Timeout expires (passing no arguments to the object's errbacks).
|
147
|
+
# Setting the status at any time prior to a call to the expiration of the timeout
|
148
|
+
# will cause the timer to be cancelled.
|
149
|
+
def timeout seconds
|
150
|
+
cancel_timeout
|
151
|
+
me = self
|
152
|
+
@deferred_timeout = EventMachine::Timer.new(seconds) {me.fail}
|
153
|
+
end
|
154
|
+
|
155
|
+
# Cancels an outstanding timeout if any. Undoes the action of #timeout.
|
156
|
+
#
|
157
|
+
def cancel_timeout
|
158
|
+
if @deferred_timeout
|
159
|
+
@deferred_timeout.cancel
|
160
|
+
@deferred_timeout = nil
|
161
|
+
end
|
162
|
+
end
|
163
|
+
|
164
|
+
|
165
|
+
# Sugar for set_deferred_status(:succeeded, ...)
|
166
|
+
#
|
167
|
+
def succeed *args
|
168
|
+
set_deferred_status :succeeded, *args
|
169
|
+
end
|
170
|
+
alias set_deferred_success succeed
|
171
|
+
|
172
|
+
# Sugar for set_deferred_status(:failed, ...)
|
173
|
+
#
|
174
|
+
def fail *args
|
175
|
+
set_deferred_status :failed, *args
|
176
|
+
end
|
177
|
+
alias set_deferred_failure fail
|
178
|
+
end
|
179
|
+
|
180
|
+
|
181
|
+
# DefaultDeferrable is an otherwise empty class that includes Deferrable.
|
182
|
+
# This is very useful when you just need to return a Deferrable object
|
183
|
+
# as a way of communicating deferred status to some other part of a program.
|
184
|
+
class DefaultDeferrable
|
185
|
+
include Deferrable
|
186
|
+
end
|
187
|
+
end
|
@@ -0,0 +1,54 @@
|
|
1
|
+
module EventMachine
|
2
|
+
|
3
|
+
# This is subclassed from EventMachine::Connection for use with the file monitoring API. Read the
|
4
|
+
# documentation on the instance methods of this class, and for a full explanation see EventMachine.watch_file.
|
5
|
+
class FileWatch < Connection
|
6
|
+
# :stopdoc:
|
7
|
+
Cmodified = 'modified'.freeze
|
8
|
+
Cdeleted = 'deleted'.freeze
|
9
|
+
Cmoved = 'moved'.freeze
|
10
|
+
# :startdoc:
|
11
|
+
|
12
|
+
def receive_data(data) #:nodoc:
|
13
|
+
case data
|
14
|
+
when Cmodified
|
15
|
+
file_modified
|
16
|
+
when Cdeleted
|
17
|
+
file_deleted
|
18
|
+
when Cmoved
|
19
|
+
file_moved
|
20
|
+
end
|
21
|
+
end
|
22
|
+
|
23
|
+
# Returns the path that EventMachine::watch_file was originally called with. The current implementation
|
24
|
+
# does not pick up on the new filename after a rename occurs.
|
25
|
+
def path
|
26
|
+
@path
|
27
|
+
end
|
28
|
+
|
29
|
+
# Should be redefined with the user's custom callback that will be fired when the file is modified.
|
30
|
+
def file_modified
|
31
|
+
end
|
32
|
+
|
33
|
+
# Should be redefined with the user's custom callback that will be fired when the file is deleted.
|
34
|
+
# When the file is deleted, stop_watching will be called after this to make sure everything is
|
35
|
+
# cleaned up correctly.
|
36
|
+
#
|
37
|
+
# Note that on linux (with inotify), file_deleted will not be called until all open file descriptors to
|
38
|
+
# the file have been closed.
|
39
|
+
def file_deleted
|
40
|
+
end
|
41
|
+
|
42
|
+
# Should be redefined with the user's custom callback that will be fired when the file is moved or renamed.
|
43
|
+
def file_moved
|
44
|
+
end
|
45
|
+
|
46
|
+
# Discontinue monitoring of the file.
|
47
|
+
# This involves cleaning up the underlying monitoring details with kqueue/inotify, and in turn firing unbind.
|
48
|
+
# This will be called automatically when a file is deleted. User code may call it as well.
|
49
|
+
def stop_watching
|
50
|
+
EventMachine::unwatch_filename(@signature)
|
51
|
+
end
|
52
|
+
end
|
53
|
+
|
54
|
+
end
|
data/lib/em/future.rb
ADDED
@@ -0,0 +1,61 @@
|
|
1
|
+
#--
|
2
|
+
#
|
3
|
+
# Author:: Francis Cianfrocca (gmail: blackhedd)
|
4
|
+
# Homepage:: http://rubyeventmachine.com
|
5
|
+
# Date:: 16 Jul 2006
|
6
|
+
#
|
7
|
+
# See EventMachine and EventMachine::Connection for documentation and
|
8
|
+
# usage examples.
|
9
|
+
#
|
10
|
+
#----------------------------------------------------------------------------
|
11
|
+
#
|
12
|
+
# Copyright (C) 2006-07 by Francis Cianfrocca. All Rights Reserved.
|
13
|
+
# Gmail: blackhedd
|
14
|
+
#
|
15
|
+
# This program is free software; you can redistribute it and/or modify
|
16
|
+
# it under the terms of either: 1) the GNU General Public License
|
17
|
+
# as published by the Free Software Foundation; either version 2 of the
|
18
|
+
# License, or (at your option) any later version; or 2) Ruby's License.
|
19
|
+
#
|
20
|
+
# See the file COPYING for complete licensing information.
|
21
|
+
#
|
22
|
+
#---------------------------------------------------------------------------
|
23
|
+
#
|
24
|
+
#
|
25
|
+
|
26
|
+
#--
|
27
|
+
# This defines EventMachine::Deferrable#future, which requires
|
28
|
+
# that the rest of EventMachine::Deferrable has already been seen.
|
29
|
+
# (It's in deferrable.rb.)
|
30
|
+
|
31
|
+
module EventMachine
|
32
|
+
module Deferrable
|
33
|
+
|
34
|
+
# A future is a sugaring of a typical deferrable usage.
|
35
|
+
#--
|
36
|
+
# Evaluate arg (which may be an expression or a block).
|
37
|
+
# What's the class of arg?
|
38
|
+
# If arg is an ordinary expression, then return it.
|
39
|
+
# If arg is deferrable (responds to :set_deferred_status),
|
40
|
+
# then look at the arguments. If either callback or errback
|
41
|
+
# are defined, then use them. If neither are defined, then
|
42
|
+
# use the supplied block (if any) as the callback.
|
43
|
+
# Then return arg.
|
44
|
+
def self.future arg, cb=nil, eb=nil, &blk
|
45
|
+
arg = arg.call if arg.respond_to?(:call)
|
46
|
+
|
47
|
+
if arg.respond_to?(:set_deferred_status)
|
48
|
+
if cb || eb
|
49
|
+
arg.callback(&cb) if cb
|
50
|
+
arg.errback(&eb) if eb
|
51
|
+
else
|
52
|
+
arg.callback(&blk) if blk
|
53
|
+
end
|
54
|
+
end
|
55
|
+
|
56
|
+
arg
|
57
|
+
end
|
58
|
+
|
59
|
+
end
|
60
|
+
end
|
61
|
+
|
data/lib/em/messages.rb
ADDED
@@ -0,0 +1,66 @@
|
|
1
|
+
#--
|
2
|
+
#
|
3
|
+
# Author:: Francis Cianfrocca (gmail: blackhedd)
|
4
|
+
# Homepage:: http://rubyeventmachine.com
|
5
|
+
# Date:: 16 Jul 2006
|
6
|
+
#
|
7
|
+
# See EventMachine and EventMachine::Connection for documentation and
|
8
|
+
# usage examples.
|
9
|
+
#
|
10
|
+
#----------------------------------------------------------------------------
|
11
|
+
#
|
12
|
+
# Copyright (C) 2006-07 by Francis Cianfrocca. All Rights Reserved.
|
13
|
+
# Gmail: blackhedd
|
14
|
+
#
|
15
|
+
# This program is free software; you can redistribute it and/or modify
|
16
|
+
# it under the terms of either: 1) the GNU General Public License
|
17
|
+
# as published by the Free Software Foundation; either version 2 of the
|
18
|
+
# License, or (at your option) any later version; or 2) Ruby's License.
|
19
|
+
#
|
20
|
+
# See the file COPYING for complete licensing information.
|
21
|
+
#
|
22
|
+
#---------------------------------------------------------------------------
|
23
|
+
#
|
24
|
+
#
|
25
|
+
|
26
|
+
=begin
|
27
|
+
|
28
|
+
Message Routing in EventMachine.
|
29
|
+
|
30
|
+
The goal here is to enable "routing points," objects that can send and receive
|
31
|
+
"messages," which are delimited streams of bytes. The boundaries of a message
|
32
|
+
are preserved as it passes through the reactor system.
|
33
|
+
|
34
|
+
There will be several module methods defined in EventMachine to create route-point
|
35
|
+
objects (which will probably have a base class of EventMachine::MessageRouter
|
36
|
+
until someone suggests a better name).
|
37
|
+
|
38
|
+
As with I/O objects, routing objects will receive events by having the router
|
39
|
+
core call methods on them. And of course user code can and will define handlers
|
40
|
+
to deal with events of interest.
|
41
|
+
|
42
|
+
The message router base class only really needs a receive_message method. There will
|
43
|
+
be an EM module-method to send messages, in addition to the module methods to create
|
44
|
+
the various kinds of message receivers.
|
45
|
+
|
46
|
+
The simplest kind of message receiver object can receive messages by being named
|
47
|
+
explicitly in a parameter to EM#send_message. More sophisticated receivers can define
|
48
|
+
pub-sub selectors and message-queue names. And they can also define channels for
|
49
|
+
route-points in other processes or even on other machines.
|
50
|
+
|
51
|
+
A message is NOT a marshallable entity. Rather, it's a chunk of flat content more like
|
52
|
+
an Erlang message. Initially, all content submitted for transmission as a message will
|
53
|
+
have the to_s method called on it. Eventually, we'll be able to transmit certain structured
|
54
|
+
data types (XML and YAML documents, Structs within limits) and have them reconstructed
|
55
|
+
on the other end.
|
56
|
+
|
57
|
+
A fundamental goal of the message-routing capability is to interoperate seamlessly with
|
58
|
+
external systems, including non-Ruby systems like ActiveMQ. We will define various protocol
|
59
|
+
handlers for things like Stomp and possibly AMQP, but these will be wrapped up and hidden
|
60
|
+
from the users of the basic routing capability.
|
61
|
+
|
62
|
+
As with Erlang, a critical goal is for programs that are built to use message-passing to work
|
63
|
+
WITHOUT CHANGE when the code is re-based on a multi-process system.
|
64
|
+
|
65
|
+
=end
|
66
|
+
|
@@ -0,0 +1,44 @@
|
|
1
|
+
module EventMachine
|
2
|
+
|
3
|
+
# This is subclassed from EventMachine::Connection for use with the process monitoring API. Read the
|
4
|
+
# documentation on the instance methods of this class, and for a full explanation see EventMachine.watch_process.
|
5
|
+
class ProcessWatch < Connection
|
6
|
+
# :stopdoc:
|
7
|
+
Cfork = 'fork'.freeze
|
8
|
+
Cexit = 'exit'.freeze
|
9
|
+
# :startdoc:
|
10
|
+
|
11
|
+
def receive_data(data) # :nodoc:
|
12
|
+
case data
|
13
|
+
when Cfork
|
14
|
+
process_forked
|
15
|
+
when Cexit
|
16
|
+
process_exited
|
17
|
+
end
|
18
|
+
end
|
19
|
+
|
20
|
+
# Returns the pid that EventMachine::watch_process was originally called with.
|
21
|
+
def pid
|
22
|
+
@pid
|
23
|
+
end
|
24
|
+
|
25
|
+
# Should be redefined with the user's custom callback that will be fired when the prcess is forked.
|
26
|
+
#
|
27
|
+
# There is currently not an easy way to get the pid of the forked child.
|
28
|
+
def process_forked
|
29
|
+
end
|
30
|
+
|
31
|
+
# Should be redefined with the user's custom callback that will be fired when the process exits.
|
32
|
+
#
|
33
|
+
# stop_watching is called automatically after this callback
|
34
|
+
def process_exited
|
35
|
+
end
|
36
|
+
|
37
|
+
# Discontinue monitoring of the process.
|
38
|
+
# This will be called automatically when a process dies. User code may call it as well.
|
39
|
+
def stop_watching
|
40
|
+
EventMachine::unwatch_pid(@signature)
|
41
|
+
end
|
42
|
+
end
|
43
|
+
|
44
|
+
end
|
data/lib/em/processes.rb
ADDED
@@ -0,0 +1,119 @@
|
|
1
|
+
#--
|
2
|
+
#
|
3
|
+
# Author:: Francis Cianfrocca (gmail: blackhedd)
|
4
|
+
# Homepage:: http://rubyeventmachine.com
|
5
|
+
# Date:: 13 Dec 07
|
6
|
+
#
|
7
|
+
# See EventMachine and EventMachine::Connection for documentation and
|
8
|
+
# usage examples.
|
9
|
+
#
|
10
|
+
#----------------------------------------------------------------------------
|
11
|
+
#
|
12
|
+
# Copyright (C) 2006-08 by Francis Cianfrocca. All Rights Reserved.
|
13
|
+
# Gmail: blackhedd
|
14
|
+
#
|
15
|
+
# This program is free software; you can redistribute it and/or modify
|
16
|
+
# it under the terms of either: 1) the GNU General Public License
|
17
|
+
# as published by the Free Software Foundation; either version 2 of the
|
18
|
+
# License, or (at your option) any later version; or 2) Ruby's License.
|
19
|
+
#
|
20
|
+
# See the file COPYING for complete licensing information.
|
21
|
+
#
|
22
|
+
#---------------------------------------------------------------------------
|
23
|
+
#
|
24
|
+
#
|
25
|
+
|
26
|
+
|
27
|
+
module EventMachine
|
28
|
+
|
29
|
+
# EM::DeferrableChildProcess is a sugaring of a common use-case
|
30
|
+
# involving EM::popen.
|
31
|
+
# Call the #open method on EM::DeferrableChildProcess, passing
|
32
|
+
# a command-string. #open immediately returns an EM::Deferrable
|
33
|
+
# object. It also schedules the forking of a child process, which
|
34
|
+
# will execute the command passed to #open.
|
35
|
+
# When the forked child terminates, the Deferrable will be signalled
|
36
|
+
# and execute its callbacks, passing the data that the child process
|
37
|
+
# wrote to stdout.
|
38
|
+
#
|
39
|
+
class DeferrableChildProcess < EventMachine::Connection
|
40
|
+
include EventMachine::Deferrable
|
41
|
+
|
42
|
+
def initialize # :nodoc:
|
43
|
+
super
|
44
|
+
@data = []
|
45
|
+
end
|
46
|
+
|
47
|
+
# Sugars a common use-case involving forked child processes.
|
48
|
+
# #open takes a String argument containing an shell command
|
49
|
+
# string (including arguments if desired). #open immediately
|
50
|
+
# returns an EventMachine::Deferrable object, without blocking.
|
51
|
+
#
|
52
|
+
# It also invokes EventMachine#popen to run the passed-in
|
53
|
+
# command in a forked child process.
|
54
|
+
#
|
55
|
+
# When the forked child terminates, the Deferrable that
|
56
|
+
# #open calls its callbacks, passing the data returned
|
57
|
+
# from the child process.
|
58
|
+
#
|
59
|
+
def self.open cmd
|
60
|
+
EventMachine.popen( cmd, DeferrableChildProcess )
|
61
|
+
end
|
62
|
+
|
63
|
+
def receive_data data # :nodoc:
|
64
|
+
@data << data
|
65
|
+
end
|
66
|
+
|
67
|
+
def unbind # :nodoc:
|
68
|
+
succeed( @data.join )
|
69
|
+
end
|
70
|
+
end
|
71
|
+
|
72
|
+
class SystemCmd < EventMachine::Connection # :nodoc:
|
73
|
+
def initialize cb
|
74
|
+
@cb = cb
|
75
|
+
@output = []
|
76
|
+
end
|
77
|
+
def receive_data data
|
78
|
+
@output << data
|
79
|
+
end
|
80
|
+
def unbind
|
81
|
+
@cb.call @output.join(''), get_status if @cb
|
82
|
+
end
|
83
|
+
end
|
84
|
+
|
85
|
+
# EM::system is a simple wrapper for EM::popen. It is similar to Kernel::system, but requires a
|
86
|
+
# single string argument for the command and performs no shell expansion.
|
87
|
+
#
|
88
|
+
# The block or proc passed to EM::system is called with two arguments: the output generated by the command,
|
89
|
+
# and a Process::Status that contains information about the command's execution.
|
90
|
+
#
|
91
|
+
# EM.run{
|
92
|
+
# EM.system('ls'){ |output,status| puts output if status.exitstatus == 0 }
|
93
|
+
# }
|
94
|
+
#
|
95
|
+
# You can also supply an additional proc to send some data to the process:
|
96
|
+
#
|
97
|
+
# EM.run{
|
98
|
+
# EM.system('sh', proc{ |process|
|
99
|
+
# process.send_data("echo hello\n")
|
100
|
+
# process.send_data("exit\n")
|
101
|
+
# }, proc{ |out,status|
|
102
|
+
# puts(out)
|
103
|
+
# })
|
104
|
+
# }
|
105
|
+
#
|
106
|
+
# Like EventMachine.popen, EventMachine.system currently does not work on windows.
|
107
|
+
# It returns the pid of the spawned process.
|
108
|
+
def EventMachine::system cmd, *args, &cb
|
109
|
+
cb ||= args.pop if args.last.is_a? Proc
|
110
|
+
init = args.pop if args.last.is_a? Proc
|
111
|
+
|
112
|
+
# merge remaining arguments into the command
|
113
|
+
cmd = ([cmd] + args.map{|a|a.to_s.dump}).join(' ')
|
114
|
+
|
115
|
+
EM.get_subprocess_pid(EM.popen(cmd, SystemCmd, cb) do |c|
|
116
|
+
init[c] if init
|
117
|
+
end.signature)
|
118
|
+
end
|
119
|
+
end
|