Vassil Dichev schrieb: >> @Daniel - maybe Vassil can help you there. What exactly was your problem? >> > > @Daniel- I realize now we intended to make the message parser > pluggable, but then there was always something which seemed more > important. I think this is the right time to get back to this issue. > The problem here is that many of the higher-level parser combinators > use common low-level combinators, i.e. email address, identifier > characters (for usernames, pool names, etc.). In order to reuse these, > it's a good idea to separate and document the low-level parser > combinators we can rely on (like an API). > The issue was to find whether/how I could reuse the patterns used to make it recognizable through the pattern.
Another way would be (in Java terms) to let each plugin via a specific check on its own how it wants to consume message content from esme. Do we see a flexible MsgParser solution any time soon or should I check with Vassil on how to hardwire amqp-support? Kind regards, Daniel
