Re: Re: Net_Gearman Problems

On Jun 5, 2008, at 9:54 AM, Travis Swicegood wrote:

If there are multiple types of encodings available in Gearman, why not have an Encoder interface that handles the encoding. You could create Net_Gearman_Encoders_JSON as the default, but then have a Net_Gearman::registerEncoder(Net_Gearman_Encoder $encoder) to allow people to use the other encodings...?

I'm against this for the simple fact that Gearman was made for performance and scalability and I see this as an unnecessary layer of abstraction that would decrease performance.

Requiring people to create an instance inside the Net_Gearman package naming is very limiting and makes use in a VCS much harder.

It should be noted here that Net_Gearman_Job_Common provides a number of helper functions that the worker relies on. I think I've addressed a way in which this could be addressed in my last email though. --Joe