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 hirsch.dick@gmail.com
 designates 72.14.220.153 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=DgZtMCO2j6pesRyenO/eqcK1V2JytcCN9GbnPNgQP7CjBdYIZgy3L0Dp7V3pQFc20P
         OsG66EAsiSYW19+HjDCfF5AFRwTt55hns2Ug+sHcH6sQ1GjHzvbrupmurlCAVV9jSrRH
         bclqIUs8M3emPCvSUcxrk1hc+v6m9R7py+aX4=
MIME-Version: 1.0
In-Reply-To: <771905290911240148idb31333r5ce1bdfda311b5e3@mail.gmail.com>
References: <771905290911231530s28817fbcpa815ddbfced8a9ad@mail.gmail.com>
	 <fa2d9f450911232145q2101f04bkf19aa37944f85dfc@mail.gmail.com>
	 <771905290911240014r69837d3ei549c061a49efa266@mail.gmail.com>
	 <c7fc82820911240117q5f6757a6ra59db4c0c48453f3@mail.gmail.com>
	 <771905290911240148idb31333r5ce1bdfda311b5e3@mail.gmail.com>
Date: Tue, 24 Nov 2009 11:20:04 +0100
Message-ID: <fa2d9f450911240220pb54c075xc3ffe63caf7beeab@mail.gmail.com>
Subject: Re: Memory allocation analysis
From: Richard Hirsch <hirsch.dick@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Posted the performance results (plus attachments) to the wiki:

http://cwiki.apache.org/confluence/display/ESME/Performance+test+2009-11-24

D.

On Tue, Nov 24, 2009 at 10:48 AM, Markus Kohler <markus.kohler@gmail.com> wrote:
> Hi Vassil,
> OK I understand, for automatically generated messages a server side
> implementation would be needed.
>
>
> Markus
> "The best way to predict the future is to invent it" -- Alan Kay
>
>
> On Tue, Nov 24, 2009 at 10:17 AM, Vassil Dichev <vdichev@apache.org> wrote:
>
>> > Basically I meant that we should just go for a simple custom formatter
>> and
>> > not try to improve the existing textile formatter.
>>
>> Agreed. It will be easiest to first add just enough formatting
>> necessary for the needs of ESME and then think about full-blown
>> parsers. Not that the latter is not worth investing in, but it will
>> take more effort.
>>
>> > David suggested ANTLR and maybe we should give it a try and write a
>> custom
>> > formatter.
>>
>> ANTLR would be nice for something where speed is important and parsing
>> is complex, like parsing scala syntax in a beautifier. For an
>> occasional comment in a blog liftweb-textile should be OK, I guess.
>>
>> > Another crazy idea that just came to my mind would be to use javascript
>> on
>> > the client side to do the formatting. Not sure whether this could be
>> easily
>> > support all the features ESME needs, but markdown formatting using
>> > javascript is possible :
>> >
>> http://stackoverflow.com/questions/1319657/javascript-to-convert-markdown-textile-to-html-and-ideally-back-to-markdown-te
>> > points to http://attacklab.net/showdown/
>> >
>> > Stackoverflow itself does on the fly formatting, which I think is a nifty
>> > feature.
>>
>> This is not a crazy idea at all, however I had the idea to apply
>> formatting to automatically generated messages, and not based on
>> lightweight formatting rules only.
>>
>