Description:
------------
Hi there, firstly thanks for this package!

From what I can see of the docs there does not appear to be a means to set the Worker client_id (part of the gearman spec).

Most other languages allow the setting of this id (which is very useful when writing a gearman monitoring suite)
i.e. http://packages.python.org/gearman/worker.html

I am considering modifying the extension myself, however would like to hear if its a feasible fix (or change depending how you view it).

Regards
Ross

Expected result:
----------------
ip: 127.0.0.1
client_id: testworker.py <-- python worker
tasks: ('reverse',)

ip: 127.0.0.1
client_id: TestWorker.php <-- php woker
tasks: ('reverse')

Actual result:
--------------
ip: 127.0.0.1
client_id: testworker.py <-- python worker
tasks: ('reverse',)

ip: 127.0.0.1
client_id: - <-- php worker - as u can see - is the id which is no good when multiple of the same worker is registered
tasks: ('reverse')