Awesome, be sure to put the Ruby API details on the gearman.org wiki (just create account/login and edit the download page). The Ruby ext that wraps the C lib is sort of "free" because we're using SWIG (get a few other dynamic languages too). It will be there if you want it, but I definitely see the value in having native language APIs too (no dependencies for cross-platform). The more options the better!
As for this original bug, could you reproduce this and dump the gearmand verbose output like I did in the previous comment? I'd like to see that the packets being sent/received when you run into the bug. I've tested this on a few platforms with the Perl exception code and have not seen an issue.
Hi Kim,
Awesome, be sure to put the Ruby API details on the gearman.org wiki (just create account/login and edit the download page). The Ruby ext that wraps the C lib is sort of "free" because we're using SWIG (get a few other dynamic languages too). It will be there if you want it, but I definitely see the value in having native language APIs too (no dependencies for cross-platform). The more options the better!
As for this original bug, could you reproduce this and dump the gearmand verbose output like I did in the previous comment? I'd like to see that the packets being sent/received when you run into the bug. I've tested this on a few platforms with the Perl exception code and have not seen an issue.
Thanks!
-Eric