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 markus.kohler@gmail.com
 designates 209.85.217.227 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=QWmvt5u3nIfMui92qnQDhvIbRVnJLnOqmooEEPCoFyOgvOac4DGoVHwRzOzoJSqL9l
         Nc5B0EBUZ78FOpfbvff+KhgwX5tUeXkioMuc0kzTOqUzTkGHA22PD2k2IH18xmEYJeQg
         dsZdbT07tU7w1AEOcmGOZSMX2XJlHEHsV7xW8=
MIME-Version: 1.0
In-Reply-To: <fa2d9f450911240220pb54c075xc3ffe63caf7beeab@mail.gmail.com>
References: <771905290911231530s28817fbcpa815ddbfced8a9ad@mail.gmail.com>
	 <fa2d9f450911232145q2101f04bkf19aa37944f85dfc@mail.gmail.com>
	 <771905290911240014r69837d3ei549c061a49efa266@mail.gmail.com>
	 <c7fc82820911240117q5f6757a6ra59db4c0c48453f3@mail.gmail.com>
	 <771905290911240148idb31333r5ce1bdfda311b5e3@mail.gmail.com>
	 <fa2d9f450911240220pb54c075xc3ffe63caf7beeab@mail.gmail.com>
Date: Tue, 24 Nov 2009 11:38:12 +0100
Message-ID: <771905290911240238x707ef2bdlbe33bab335443ec3@mail.gmail.com>
Subject: Re: Memory allocation analysis
From: Markus Kohler <markus.kohler@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e641de50fa72f304791b89bd

--0016e641de50fa72f304791b89bd
Content-Type: text/plain; charset=ISO-8859-1

Thanks!
Markus
"The best way to predict the future is to invent it" -- Alan Kay


On Tue, Nov 24, 2009 at 11:20 AM, Richard Hirsch <hirsch.dick@gmail.com>wrote:

> 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.
> >>
> >
>

--0016e641de50fa72f304791b89bd--