Ben Meynell comments

Results 37 comments of


                                            Ben Meynell

Less variables not imported globaly

Same issue here

[Call For Help] - New maintainers for that Package

@mmoreram - Maybe interested... If I can convince my current company to switch from beanstalk to gearman (or use them both). What are you using these days?

Added emission of kernel events for GearmanJob lifecycle

Is there an issue number or link to discussion anywhere prompting this PR? Curious about background/context.

Added emission of kernel events for GearmanJob lifecycle

@Eloar - I see you included some documentation in your PR. Could you leverage that to create a GH issue and then associate this PR to that issue? My knee-jerk...

Define job callable name per Annotation

I have been flummoxed by this behavior as well. **Fundamental Question:** > **Can the archetypal example, [_reverse_](http://gearman.org), be replicated with this bundle?** **Example Code** _(copied verbatim from the [gearman.org](http://gearman.org/) home...

Check job is running before call.

> I would have liked the client to know that the job is available prior to attempting a job on it. I don't understand ... what is the use case?

[RFC] Ideas - Set of recipes to show some examples.

Map/Reduce example

GearmanClient::do*('namespace.name', '') error

:+1: but I'd like to see the gearman docs about this. BTW why was this closed?

GearmanClient::do*('namespace.name', '') error

I personally don't like getting errors directly from the daemon like `Warning: GearmanClient::doNormal(): add_task(GEARMAN_INVALID_ARGUMENT) invalid workload -> libgearman/add.cc:199` ... @mmoreram should this bundle catch this situation instead and throw its...

GearmanClient::do*('namespace.name', '') error

... or add a setting that automatically puts in a 0 for blank workloads ...