esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Pollak <>
Subject Re: ESME Groups
Date Fri, 13 Mar 2009 10:59:55 GMT
On Fri, Mar 13, 2009 at 10:37 AM, Vassil Dichev <> wrote:

> Great, I was anxious to hear David's opinion about pools.
> It seems I got the right idea on at least 2 counts:
> -pools are not about resending messages (we already have that)
> -access restrictions in a pool apply to messages, not to people
> @David, If I understand correctly, a message can only be in one pool,
> right? (1-to-1 relationship). That would fit Bill's description, as
> well


A message may only be in one pool.  There is no way for a message to escape
the pool (eg. resend cannot change the pool) and any replies (or comments in
FB parlance) are in the pool of the original message (this is for
performance and security purposes.)

> @Dick, It's true that the pools functionality is spread in both server
> and UI, but the biggest difficulty I had in mind was not splitting the
> functionality into bite-sized chunks. It's coming up with and agreeing
> on the concept, such that it fits the design and purpose of ESME.

Lift, the simply functional web framework
Beginning Scala
Follow me:
Git some:

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