Issues - purzelrakete/workling

purzelrakete / workling

451

Description:

easily do background work in rails, without commiting to a particular runner. comes with starling, bj and spawn runners.

Sort by: Priority | Votes | Last Updated

Loading…

1.

2 votes

Although advanced clients are optional, Workling won't run without their dependencies.
1 comment Created 6 months ago by lachie

Title

Body
For example, I am running cucumber features, hoping to use the NotRemote runner. Workling was crashing because it was trying and failing to load the starling runner anyway. I didn't have a memcache client lib installed it fell over! I'll look into making a patch, just wanted to let you know sooner.
or cancel

For example, I am running cucumber features, hoping to use the NotRemote runner.

Workling was crashing because it was trying and failing to load the starling runner anyway.

I didn't have a memcache client lib installed it fell over!

I'll look into making a patch, just wanted to let you know sooner.

Comments

masonlee Wed Jun 17 18:25:49 -0700 2009 | link

Yeah, all that stuff is pretty easy to rip out. IMHO, Workling should just skip trying to automatically detect various clients and instead require explicit setup in the config, defaulting to NotRemoteRunner.

Comment
Yeah, all that stuff is pretty easy to rip out. IMHO, Workling should just skip trying to automatically detect various clients and instead require explicit setup in the config, defaulting to NotRemoteRunner.
or cancel

Parsed with GitHub Flavored Markdown
2.

1 vote

Warning about using the tmm1-amqp library in workling
1 comment Created 5 months ago by masonlee

Title

Body
I'd like to make a friendly caution against using the tmm1-amqp client for workling. It's an elegant library for doing highly concurrent stuff, and is perhaps suitable for the invoker side of the workling client, but for making calls to "publish", using a synchronous AMQP client makes handling things like connection problems a lot easier. The amqp client here will just die on you with no exceptions to workling. Aman Gupta (tmm1) has recommended to use "Bunny" (or also "Carrot") for this rather than tmm1-amqp, and I now have a Bunny Workling client in production. It's a very simple library. Bunny: http://github.com/celldee/bunny/tree/master
or cancel

I'd like to make a friendly caution against using the tmm1-amqp client for workling. It's an elegant library for doing highly concurrent stuff, and is perhaps suitable for the invoker side of the workling client, but for making calls to "publish", using a synchronous AMQP client makes handling things like connection problems a lot easier. The amqp client here will just die on you with no exceptions to workling.

Aman Gupta (tmm1) has recommended to use "Bunny" (or also "Carrot") for this rather than tmm1-amqp, and I now have a Bunny Workling client in production. It's a very simple library.

Bunny: http://github.com/celldee/bunny/tree/master

Comments

dansketcher Sun Nov 15 17:24:37 -0800 2009 | link

I've implemented a Workling fork that supports Bunny and Carrot through a SyncAmqpClient, and also an associated return store.
See here: http://github.com/touchlocal/workling

Comment
I've implemented a Workling fork that supports Bunny and Carrot through a SyncAmqpClient, and also an associated return store. See here: http://github.com/touchlocal/workling
or cancel

Parsed with GitHub Flavored Markdown
3.

2 votes

Include these Capistrano start/stop tasks with Workling code?
0 comments Created 5 months ago by masonlee

Title

Body
http://thinkrefresh.com/posts/9-starling-workling-capistrano-tasks
or cancel

http://thinkrefresh.com/posts/9-starling-workling-capistrano-tasks

Comments

Parsed with GitHub Flavored Markdown
4.

0 votes

Incompatibility with ruby 1.8.5
0 comments Created 3 months ago by loki

Title

Body
Since version 0.4.2.1 workling is broken when used with ruby 1.8.5. Maybe a warning/requirement in the README should be provided. More info in the commit comments http://github.com/purzelrakete/workling/commit/fab77363c56e381d4650947fc7ac2bd05323aab5
or cancel

Since version 0.4.2.1 workling is broken when used with ruby 1.8.5. Maybe a warning/requirement in the README should be provided. More info in the commit comments http://github.com/purzelrakete/workling/commit/fab77363c56e381d4650947fc7ac2bd05323aab5

Comments

Parsed with GitHub Flavored Markdown

Labels

Although advanced clients are optional, Workling won't run without their dependencies.

Comments

Warning about using the tmm1-amqp library in workling

Comments

Include these Capistrano start/stop tasks with Workling code?

Comments

Incompatibility with ruby 1.8.5

Comments