Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates
 74.125.78.145 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=hhVY89G74+QtmFHaPXF0qkzQYVC0Q15ZSHBa4kD9gXjvKqmguNYC6yGewOgXEUra91
         Hrn6GYUQLrCckiHDLJ8QeUX4higKbOl0WJrW38gMu8prCQ+zqFuJfFT5udeApYJzUDi7
         kP0bdxrQrYUw1VwsNyc+6cgSlocl4jDwrTZYg=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <cdbebedf0911290635o56ed920fo417849a945db0ff2@mail.gmail.com>
References: <771905290911290209j22ae75cfxb147a09af309b0b6@mail.gmail.com>
	 <771905290911290252i30364774oa5931e07b914efff@mail.gmail.com>
	 <771905290911290258s7b3e449j88aedcad73abef10@mail.gmail.com>
	 <c7fc82820911290503j48c832aalead7d15f7041c712@mail.gmail.com>
	 <cdbebedf0911290635o56ed920fo417849a945db0ff2@mail.gmail.com>
Date: Sun, 29 Nov 2009 19:26:33 +0200
Message-ID: <c7fc82820911290926v11011434lb81919fdf0134025@mail.gmail.com>
Subject: Re: We are down to 4.6 Mbyte
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> I am sorry you feel embarrassed. =A0While bugs happen, your effective cod=
e to
> bug ratio is quite excellent... and this is the kind of bug we like to ha=
ve:

Thanks for the kind words. I feel relieved we found the bug as well,
of course, but the first reaction was mild annoyance that I caused
some lost time debugging, including for myself. I just wanted to
correct the others that "making ESME 5000 times better" is not the
complete picture ;-) I didn't change the design or make significant
refactoring, for example.

I also wanted to tell my story as a learning experience for others-
things don't always seem so straightforward as they seem. It's exactly
as you said- people are often prone to jump to conclusions about
Scala, Lift, REST, databases, cache, sessions, etc. It happens every
day.

It just occurred to me that we can add another point to our design
philosophy page- measure and test extensively before making
conclusions about the merit of a certain technology or pattern.

> So, in the future, we definitely need more tests (both as part of the
> development process and integration/performance tests). =A0We also need t=
o
> work together to address the results of the tests. =A0Results of a single=
 test
> should not be viewed as a repudiation of a design. =A0Tests should be
> invitations to either fix a bug (as in this case) or in the event that a =
bug
> cannot be fixed without significant refactoring, a reasoned discussion of
> the merits and likely performance implications of another design.