On Mon, Nov 1, 2010 at 10:42 AM, Andrew Ballard <aball...@gmail.com> wrote:

> Right up to here, it sounded more like an interface than an abstract base
> class.

I think there's an interface in there *and* a basic (HTTP? RPC?)
implementation that receives and dispatches the messages. I would split
these responsibilities into two separate classes which would allow you to
wire up the services to different dispatchers over time.

But to your original question, Richard, I agree with Nathan. Go with the
solution that is both easy to code and and easy to read, especially given
that the API is quite static.


Reply via email to