This is a short history lesson and personality profile of two of the active developers who have been here for some time. The purpose of this email is to explain a little of the dynamic that Leo had responded to in his email.
I joined Avalon a few months ago because I was impressed with Cocoon's framework. I later found out that the framework was built on Avalon. I since took it on myself to learn and document the framework as it was at that point. This was a contribution that Federico (the project lead for the Avalon Framework) appreciated since he admitted he wasn't the greatest documentor. At that point, I have been keeping Avalon and Cocoon in synch till now. A couple of months later (and I understood Avalon pretty well by then), a bright developer named Peter joined the mailing list. He had a different background than I did, I was focused on enterprise solutions, and he was focused on game servers. Having worked with another bright game developer in the past, I recognized that lessons learned in game servers will also apply in enterprise solutions. The interesting thing is that Peter had developed a framework independantly which he called Telenon that was _very_ close to the Avalon framework. I spent alot of time trying to convince him to join forces. Eventually, he did (although I don't take sole credit for that decision). Early on, I discovered something about Peter that is both his strength and his weakness: he is a very strong personality. It is his strength because when we are all on the same page, he is a tremendous ally. It is his weakness because he is slow to accept different viewpoints. I also am strong personalitied, though not as much as Peter. What you may see in our emails are personal joking and good natured prodding toward each other. Some people might be offended by some of the things we say, however we take it in it's proper meaning. Peter and I have gone head to head on a few points, including the way we use the ComponentManagemer and ComponentSelector today. Federico was also in on this conversation, so we hashed out some key details. At that time, I favored JNDI because of enterprise familiarity, Federico favored simple ComponentManager because of simplicity, and Peter favored ComponentManager/NamedComponentManager because of a defined need. The need stated was there are times where we have multiple components that need to be chosen during runtime that fit the same role. The end solution was better than any of our original proposals or ideas. Many times, the point that Peter and I may disagree upon has to do with the semantics of the proposal, and not necessarily the entire concept. Because both Peter and I can be stubborn, we bring out each other's best ;). But it also forces us to declare our reasoning more explicitly. Eventually we do get on the same page and champion each other's cause. I believe Peter and I have the utmost respect for each other. He is very good at what he does, and we provide a reality check for each other. Leo's concerns regarding what boils down to seemingly childish "I'm right, your wrong" statements is well taken--however most of you see them outside of the context of the (recent) history of Avalon. I won't post any followups of this email, and if anyone feels compelled to put in their two cents, I request that you limit it to one email. That way, your viewpoint is established, and this does not degenerate into a mud slinging contest and noise on the list is minimized. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
