An acquaintance is designing an important API. One function takes a Handler class. I advised him that the API should instead take any object that implements the IHandler interface. I find that APIs that take objects tend to force architecture (see XNA). His argument is that you (the user of the API) are free to override any method you like, and leave the default functions to handle everything else. My suggestion is to provide a class that implements IHander, and we are free to use it if we want. I would like APIs that don't spend my base class. I know Karl has an opinion about this.
-- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
