incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Pollak" <feeder.of.the.be...@gmail.com>
Subject Re: [ESME-dev] Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
Date Thu, 06 Nov 2008 14:04:16 GMT
On Thu, Nov 6, 2008 at 3:13 AM, Darren Hague <dhague@fortybeans.com> wrote:

>
> Hi Ian,
>
> One of the value-added aspects of ESME is in the server-side logic, which
> allows users to set up rules & behaviours (e.g. "only send me messages from
> X if they are tagged Y", and "email me when someone starts following me").
> Also, there is a fundamental difference in attitude between broadcast &
> subscribe: XMPP/Jabber and email are used to send messages *to* people; ESME
> and other microsharing solutions are more about end users deciding who they
> want to hear *from*. Having said that, there is a sense in which we are
> somewhere in the middle of a continuum that has email at one end and IM at
> another. Even so, we think we occupy a niche with strong demand, especially
> for enterprise-grade levels of security and control over messaging - none of
> which is present in IM or email solutions.
>
> Please have a read through the articles at http://blog.esme.us/ for more
> about what makes us different & valuable.


In addition, the choice of transport (HTTP or XMPP) does not speak to the
format of the enclosed message. There is a lot of specific stuff in the
communication protocol.  The format of the message (signing, encryption,
etc.) is the thing of value, not the way the bytes are moved.

In terms of actual implementations of HTTP and XMPP, I lean towards HTTP for
a number of reasons:

   - There is only one reasonable open source XMPP implementation for the
   JVM: OpenFire.  OpenFire in my experience has a ton of bugs.  On the other
   hand, there are a number of good client and server packages for HTTP.
   - ESME instances will already be running on an HTTP port.  Adding an XMPP
   port to the mix as a requirement for federation means opening yet more ports
   in firewalls.  This is a non-trivial administrative burden.

With that being said, having an add-on to ESME that allows XMPP transport
for federated messages and/or for internally generated user messages (my
Twitter use dropped significantly after they stopped support XMPP) is
something we could add to the backlog.

Thanks,

David


>
>
> Best regards,
> Darren
>
>
> >Hi.
> >
> >don't take this the wrong way, but what is wrong with XMPP and jabber
> >for this kind of thing? wouldn't it make more sense to just extend that?
> >
> >
> >
> >Darren Hague wrote:
> >> I would like to propose ESME as a project for the Apache Incubator.
> >>
> >> Enterprise Social Messaging Experiment (ESME) is a secure and highly
> >> scalable microsharing and micromessaging platform that allows people
> >> to discover and meet one another and get controlled access to other
> >> sources of information, all in a business process context. ESME is
> >> written in Scala and uses the Lift web framework.
> >>
> >> Please see http://wiki.apache.org/incubator/ESMEProposal for details.
> >>
> >> Since this is my first Apache project, any and all feedback is welcome
> >> - I will call for a vote a few days after relevant messages on the
> >> list reduce to a trickle and people seem happy with the proposal.
> >>
> >> Best regards,
> >> Darren Hague
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
>
> --
> darren.hague@fortybeans.com
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "esme-dev" group.
> To post to this group, send email to esme-dev@googlegroups.com
> To unsubscribe from this group, send email to
> esme-dev+unsubscribe@googlegroups.com<esme-dev%2Bunsubscribe@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/esme-dev?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>


-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message