<div class="gmail_quote">On Sun, Feb 27, 2011 at 22:06, Cody Lerum <span dir="ltr"><<a href="mailto:cody.lerum@gmail.com">cody.lerum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Now that I think about it, implementing it as an interface would cut<br>
the method count down on the MailMessage/VelocityMailMessage<br>
interfaces quite a bit...and from a maintenance perspective I'm<br>
worried about those getting too large since many of the methods have<br>
to be replicated on MailMessage + VelocityMailMessage and any future<br>
Templating systems we support. Or we just drop the builder pattern all<br>
together.<br>
<br>
I skeptical of someone implementing the EmailAttachment interface on<br>
their own, but it can't hurt and will make the api cleaner.<br></blockquote><div><br></div><div>+1</div><div><br></div><div>I can't think of a case when someone said "dang it, I made too many interfaces". In fact, I usually want to club someone over the head for forcing me to replace a whole subsystem because the author failed to make use of an interface.</div>
<div><br></div><div>-Dan</div><div> </div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>