Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Date: Mon, 11 Jun 2007 17:19:35 -0400
From: Bob Scheifler <Bob.Scheifler@Sun.COM>
Subject: Re: SourceAliveRemoteEvent Part II
In-reply-to: <466AF229.7020402@cheiron.org>
Sender: Bob.Scheifler@Sun.COM
To: river-dev@incubator.apache.org
Reply-to: Bob.Scheifler@Sun.COM
Message-id: <466DBC67.9000803@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <465C83B4.9020008@dcrdev.demon.co.uk>
 <465D8E2C.7090503@cheiron.org> <46648B68.6030904@Sun.COM>
 <4664A018.4010903@cheiron.org> <4665A783.8040004@Sun.COM>
 <466676B4.30809@cheiron.org> <4666EF37.9090307@Sun.COM>
 <1181155708.3134.80.camel@cameron> <466714E4.3070501@cheiron.org>
 <46688C26.2090000@Sun.COM> <46690FDA.2040104@cheiron.org>
 <4669B201.2030804@Sun.COM> <466AF229.7020402@cheiron.org>
User-Agent: Thunderbird 1.5.0.5 (X11/20060731)

Mark Brouwer wrote:
> My definition could be best described as "The set of those quantitative
> and qualitative characteristics of a distributed (multimedia) system,
> which are necessary in order to achieve the required functionality of an
> application." [1]
> 
> Based on the above definition I find the constraint for SARE a
> reasonable QoS constraint.

I don't get how asking for SARE events translates into a quantitative
or qualitative characteristic, could you explain?  I also don't understand
why SARE event selection is QoS, but other event selections are not.

> As mentioned in the footnote in the response to Dan, if there is a
> better mechanism for catering what I would call QoS aspects, both at the
> method and proxy level, I'm all ears.

If SARE is an example, then method arguments seem a better mechanism.

The way I think of QoS, it additionally seems peculiar to be putting
QoS constraints on the event registration to affect event delivery;
QoS on event delivery should be done by placing constraints on the
event listener.

- Bob