A belated +1.
Steve Graham wrote:
Hi Sanjay:
I think you understand the issue, at
least as I understand it.
It seems we are inconsistent in
BaseN
on the extensibility of most of our message exchanges.
The following messages do not have
extensibility:
NotificationConsumer::Notify
NotificationProducer::Subscribe
NotificationProducer::SubscribeResponse
NotificationProducer::GetCurrentMessage
The following messages have
extensibility:
NotificationProducer::GetCurrentMessageResponse
SubscriptionManager:PauseSubscription
SubscriptionManager:PauseSubscriptionResponse
SubscriptionManager:ResumeSubscription
SubscriptionManager:ResumeSubscriptionResponse
So I guess a better way to consider
the issue of consistency is whether we should add extensibility to all
the messages, or whether we should remove it where it appears.
My vote would be to add
extensibility
to Notify, Subscribe, SubscribeResponse and Get CurrentMessage.
sgg
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, IBM Software Group, Web services and SOA
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++
"Patil, Sanjay" <sanjay.patil@sap.com>
wrote on 04/25/2005 03:20:57 PM:
> Hi Steve,
>
> As discussed on today's conf-call, I will be
adding a new issue to our log. In that
> regard, I wanted to quickly verify my understanding of the issue
...
>
> Is this issue regarding the extensibility of
the Publisher Registration messages?
> That is, we want to have an ability to add open content to the
> RegisterPublisherRequest and RegisterPublisherResponse messages!
However
we do not
> seem to have such an extensibility for most of the other messages,
for example,
> SubscribeRequest or SubscribeResponse do not allow open content
(as
first class
> child elements). So I am not sure what you mean by "consistency"
below. Perhaps I
> have entirely misunderstood the issue.
>
> Thanks,
> Sanjay
> -----Original Message-----
> From: Steve Graham [mailto:sggraham@us.ibm.com]
> Sent: Wednesday, Apr 20, 2005 18:23 PM
> To: wsn@lists.oasis-open.org
> Subject: [wsn] [wsn potential issue] Open content on Publisher
Registration
>
> It was pointed out to me by a colleague that there is no
extensibility
on Publisher
> Registration. I suggest we add one for consistency of
extensibility.
Please
> consider this request to raise an issue on the
WS-BrokeredNotification
specification.
>
> sgg
>
> ++++++++
> Steve Graham
> (919)254-0615 (T/L 444)
> STSM, IBM Software Group, Web services and SOA
> Member, IBM Academy of Technology
> <Soli Deo Gloria/>
> ++++++++
|