Craig, >Paul, this needs to be turned around as well. *Please* consider that what >you are asking for has a very substantial backwards compatibility cost -- >making this change would mean it's impossible to have compiled Java code >that works with both 4.0.1 and 4.0.2, because the class inheritance of the >Embedded class would change. We just went through this trying to undo the >poor factoring of org.apache.net.ServerSocketFactory -- in the end, we had >to undo an obviously beneficial change for this reason. > Sorry dude, I was only considering the rolling forward of features. I did not realise that 4.0.1 was still a factor. I thought that the additon of an interface (without renaming anything) was completely safe. I stand corrected.
>It is not appropriate to break binary compatibility in the 4.0 branch. >Breaking it between 4.0 and 4.1-dev is not necessarily as absolute, but >the penalty is still severe. > I'll check back again in some months. For now, I'll put my "must sepserate interface and impl' axe away and let you dude get on with the flagship effort. Keep up the good work... Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
