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 vdichev@gmail.com designates
 209.85.219.209 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=p7LH4AjpggrlbMOPZXDCth/wFCEUt9sjJBnYH9j6Uv64VCVL+mHSAwM+r7i09K2ugH
         T2zFbWm38kzXEzO6QW/WJ9tqcG12Omb2ccuuCoGHZM+c/uch+F5hs5j0Au60mP1mdQ+s
         4BG5OeVU6ypi7HMqQhDpm2ble+gMkIBAQ1b+0=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <cdbebedf0911040914w53014c35qad318a9bda4eb6b6@mail.gmail.com>
References: <68f4a0e80910251728te9c1248j10f1aa99c9f7cd2e@mail.gmail.com>
	 <68f4a0e80910270917r408588fbva0f47e73125afa4d@mail.gmail.com>
	 <771905290911031021n6aa33b53q1532c04601fd6433@mail.gmail.com>
	 <c7fc82820911032328t63ac734cx97616507b902d2ef@mail.gmail.com>
	 <771905290911040043p61039939r99b3d1a602a92e8f@mail.gmail.com>
	 <c7fc82820911040105t4da6857i9b98c01fdc0db632@mail.gmail.com>
	 <771905290911040158v539c016em1221acf54bbb5509@mail.gmail.com>
	 <cdbebedf0911040635y76afdeb5yd24640026b613381@mail.gmail.com>
	 <771905290911040809n24ad6a6ey9a00c1d819dfbb15@mail.gmail.com>
	 <cdbebedf0911040914w53014c35qad318a9bda4eb6b6@mail.gmail.com>
Date: Wed, 4 Nov 2009 20:14:47 +0200
Message-ID: <c7fc82820911041014y33036dd2vda4ce00da23e3ab6@mail.gmail.com>
Subject: Re: Patch submitted, working towards API design
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

OK, let's start the discussion again. For the API calls which are not
comet-related, ESME could benefit to apply the RESTful principles
which make sense.

As for Comet, my team has rejected Yammer in the past for short
scrum-like meetings of remote teams because if everyone has to wait
what the others have to say, the meeting is prohibitively long (and it
takes less than 30 seconds to update one message). I don't claim that
everyone has this need or even that we're not trying to fit a tool
into a scenario it wasn't meant to do. But it sure is one of the cool
factors for everyone I've demoed ESME to. If we're not different than
the competition- laconi.ca, Yammer, present.ly, etc., then I'm not
sure we can compete just on the speed of copying features from the
others.

At any rate, time will tell if Comet is a key differentiator or is
dragging us down. But since we have it already, why would we give it
up?

I would even suggest that we have both APIs compete with each other
and see which one clients would choose to use.

Vassil