@Michael:
A couple of weeks ago we had a very interesting discussion ref
sessions and RESTful APIs.
If you find the time, I suggest you read it as it does a good job
explaining ESME's design.
http://www.mail-archive.com/esme-dev%40incubator.apache.org/msg01766.html
(Read the mails which start with Markus' answer.)
/anne
On 26. nov. 2009, at 10.28, Richard Hirsch wrote:
Good idea about having the user decide what parser to use. I'm also
assuming that bold and italic should be enough
On Thu, Nov 26, 2009 at 10:25 AM, Vassil Dichev <[email protected]>
wrote:
@Markus It would be interesting to remove the Textile parser and do
the tests again.
This would confirm whether it is the culprit or not. If I remember
correctly, it was just a change in one line of code.
Just found the change
(http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/scala/org/apache/esme/model/Message.scala?r1=804817&r2=819509&diff_format=h
)
You could change the code to the older version and try it again
there have been a couple of changes afterwards, but just drop the
whole Text case and there you go.
I'm on it. I'll try to have just *bold* and _italic_ so far, does
anyone need anything else? I might also make it configurable if you
want to use the Textile parser and the native parser.
