search for: next_tick

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

...;' > what(): unable to reap subprocess > Abort trap > The following code is called to connect the pipe: EventMachine::run do > # Open the connection to the dvipng shell command > EventMachine::popen $mock_dvipng_executable, > Workers::DviToPng::PipeProtocol > EM::next_tick { > EventMachine::add_timer(3) { EventMachine::stop; violated("Event loop > took too long.") } > } > end > This bug seems to happen on the first or second attempt, and then it magically goes away. Any ideas? Thanks, Duane Johnson -------------- next part ----------...

...56:26) Emitted 'error' event at: at Socket.socketErrorListener (_http_client.js:392:9) at Socket.emit (events.js:198:13) at emitErrorNT (internal/streams/destroy.js:91:8) at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) at process._tickCallback (internal/process/next_tick.js:63:19) events.js:174 throw er; // Unhandled 'error’ event Where “ stream_url” is the real ogg stream url. Also I have noticed, that if change stream_url on some another working ogg stream (not mine, just found via Google), no error occurs anymore. IceCast error log says nothing about...

...ata)->timestamp - priv->time; } else { return G_MAXUINT64; } @@ -277,24 +279,26 @@ swfdec_player_get_next_event_time (SwfdecPlayer *player) void swfdec_player_add_timeout (SwfdecPlayer *player, SwfdecTimeout *timeout) { + SwfdecPlayerPrivate *priv; GList *walk; SwfdecTick next_tick; g_return_if_fail (SWFDEC_IS_PLAYER (player)); g_return_if_fail (timeout != NULL); - g_return_if_fail (timeout->timestamp >= player->time); + g_return_if_fail (timeout->timestamp >= player->priv->time); g_return_if_fail (timeout->callback != NULL); + priv = p...

...tamp > tb->timestamp) - return 1; - return 0; -} - /** * swfdec_player_add_timeout: * @player: a #SwfdecPlayer @@ -143,6 +129,7 @@ swfdec_timeout_compare (gconstpointer a, void swfdec_player_add_timeout (SwfdecPlayer *player, SwfdecTimeout *timeout) { + GList *walk; SwfdecTick next_tick; g_return_if_fail (SWFDEC_IS_PLAYER (player)); @@ -152,7 +139,13 @@ swfdec_player_add_timeout (SwfdecPlayer SWFDEC_LOG ("adding timeout %p", timeout); next_tick = swfdec_player_get_next_event_time (player); - player->timeouts = g_list_insert_sorted (player->timeouts,...

...player->time); g_return_if_fail (timeout->callback != NULL); - SWFDEC_LOG ("adding timeout %p", timeout); + SWFDEC_LOG ("adding timeout %p in %"G_GUINT64_FORMAT" msecs", timeout, + SWFDEC_TICKS_TO_MSECS (timeout->timestamp - player->time)); next_tick = swfdec_player_get_next_event_time (player); /* the order is important, on events with the same time, we make sure the new one is last */ for (walk = player->timeouts; walk; walk = walk->next) { @@ -321,6 +322,12 @@ swfdec_player_perform_external_actions ( SwfdecPlayerAction *action...

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.