My goal here is to reduce the amount of code needed to implement Z_S_A and talk to Audioscrobbler, nothing more. But I find your other comments interesting.

Firstly, I don’t see what I’m doing here as ‘further complicating the API’. I’m trying to cut down on the ridiculous amount of code I used in the original implementation. The current set of methods for Z_S_A is not about to go away, I’m just going to use the magic of __call() to filter those requests to a much smaller subset of code, nothing more. It’s not about changing the API, it’s about reducing the amount of code needed to get the job done.

As for killing autocompletion for IDE’s, that’s not something I ever worry about.

Once I have something more concrete I will post to the Zend Framework mailing list. I think all that will really be argued about is the names of the methods, nothing more.

I can tell you that your proposed solution is not the way to go with your refactoring. The problem with your original design is the fact that it’s coupled so closely to Audioscrobbler’s API. The solution that you give here would further complicate the API and kill autocompletion for IDEs.

If you haven’t already, post about this to the mailing list, or even submit it as a proposal. I’ll try to give more detailed feedback than the first round. Darby was on the right track with getChart(), though.

Good luck with the refactor.