wsn message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [wsn] Roles vs. Port Names
- From: Steve Graham <sggraham@us.ibm.com>
- To: David Hull <dmh@tibco.com>
- Date: Mon, 9 Aug 2004 14:37:12 -0400
sgg comments
David Hull <dmh@tibco.com> wrote on 08/09/2004
12:23:32 PM:
> Alan's clarification of use cases contains the following statement:
"Note that in
> my view, the Subscription Manager and Subscriber are actually the
same entity."
Yes, I was curious about that. As the roles are defined in the whitepaper,
the
subscriber tends to be a requestor side role. The
subscription manager is the role
(also embodied as a portType) that "manages"
subscription Ws-Resources.
> I'm not entirely sure what this means, but from the use cases itself
I believe the
> point is that whatever is sending subscribe requests, control and
query messages is
> effectively managing the subscription and should be regarded as the
subscription manager.
We call that role a subscriber.
<snip>
>
> I've been thinking for a while about what might be better, but given
that different
> people process information differently, there is no objectively clear
choice.
Indeed. No objectively clear choice on a different
naming convention, so lets stick
with the convention we have, warts and all.
sgg
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]