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 robertburrelldonkin@gmail.com
 designates 209.85.218.171 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:content-transfer-encoding;
        b=jA5VD484U6z/Porh/sCVj8cITHm6tM5gkXmGsd0DkGJ0IWy1ER3N/lSDT32UQ8mvYy
         eohgY3eU0QoCiYxX9flezrI4Q98s/MxHbjKu2xdWMLtdxB1ltj/n/S/5smgLMxeZs/Gb
         nhNHpaRS0HmZ1Xa97htqHyYLWFUGkdatCXgcA=
MIME-Version: 1.0
In-Reply-To: <cdbebedf0903190649x13038d5arf6d1826cbd41f359@mail.gmail.com>
References: 
 <30DB6ACF50A0A3439F39EFEB1C52E166078F233F@nets13ja.ww300.siemens.net>
	 <30DB6ACF50A0A3439F39EFEB1C52E16607CB9F83@nets13ja.ww300.siemens.net>
	 <p06240860c5e64880d246@192.168.0.65>
	 <30DB6ACF50A0A3439F39EFEB1C52E166078F237F@nets13ja.ww300.siemens.net>
	 <f767f0600903180142g1854884bg224aaf7bc37496a1@mail.gmail.com>
	 <167204d20903180532n6732a5f0r6e7c774ed3534b8@mail.gmail.com>
	 <f767f0600903180856o5d467e54r3f4fe490c4f9d3f7@mail.gmail.com>
	 <30DB6ACF50A0A3439F39EFEB1C52E166078F238A@nets13ja.ww300.siemens.net>
	 <167204d20903190159i28a08f2ehe9d94c8bab9a0e2f@mail.gmail.com>
	 <cdbebedf0903190649x13038d5arf6d1826cbd41f359@mail.gmail.com>
Date: Thu, 19 Mar 2009 14:47:48 +0000
Message-ID: <f470f68e0903190747u3c7beeedqfc0aa167477269d8@mail.gmail.com>
Subject: Re: Ideas concerning RabbitMQ - ESME Integration
From: Robert Burrell Donkin <robertburrelldonkin@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 19, 2009 at 1:49 PM, David Pollak
<feeder.of.the.bears@gmail.com> wrote:
> On Thu, Mar 19, 2009 at 1:59 AM, Alexis Richardson <
> alexis.richardson@gmail.com> wrote:
>
>> Great. =A0What sorts of scenarios would be most interesting for you guys=
?
>
>
> To my mind:
>
> =A0 - A virtual ESME user is really the surfacing of a RabbitMQ queue (or
> =A0 collection of them) so that systems that talk to Rabbit can also be s=
ystems
> =A0 that talk to ESME
> =A0 - A filter action that puts a message into a Rabbit queue so that I c=
an
> =A0 create a rule that filters a lot of disparate data streams into somet=
hing
> =A0 that can then be sent off to other systems that listen to Rabbit
>
> There are a couple of features that these imply:
>
> =A0 - Multiple "users" per log in account. =A0If I'm going to channel a R=
abbit
> =A0 queue (or set of queues), I want a separate ESME user that people can
> =A0 follow, but I don't want to have separate login credentials.
> =A0 - The filter language needs to be a lot like spreadsheet formula
> =A0 functions because those are what business people can best deal with..=
. or
> =A0 like HyperCard statements

filter languages are quite an interesting topic

sieve would be reasonable applicable (and it's probably worth looking
at even if another approach is picked int the end). it's syntax is a
little unintuitive but AIUI it's used by several BigCo SMTP servers
and some CMS so it can't be that bad. mostly, they wrap a AJAX web
application around it.

a proof-of-concept using apache jsieve and sieve as the filter
language should be quick and easy to do

- robert