Steve Graham wrote:
I thought we agreed to make the
topics
component optional in the Notify.
Right ... so you can leave that out if you want. The question is, can
you put anything else in if you want? I had thought there was open
content, but there doesn't seem to be.
The other question is to what extent the core needs to talk about
topics at all, or if you prefer, to what extent are topics "just
another filter"?
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, IBM Software Group, Web services and SOA
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++
Steve Graham wrote:
+1 to Sanjay.
We had the notion of filter previously (we called it selector) but did
not choose to add it to the "metadata" in the Notify message.
I don't see that anything has changed to compel us to rethink this
bit.
So what's so special about topics? Also, wasn't
that decision taken prior to making topics optional?
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 05/26/2005 04:20:40 PM:
>
> Filters are part of Subscribe message, where as Topic is a Notify
> metadata. I don't see the connection.
>
> Thanks,
> Sanjay
>
> >-----Original Message-----
> >From: David Hull [mailto:dmh@tibco.com]
> >Sent: Thursday, May 26, 2005 13:17 PM
> >To: wsn@lists.oasis-open.org
> >Subject: [wsn] Topic/filter metadata in Notify message
> >
> >
> >The Notify message (actually, the metadata that may be used
with
either
> >Notify or raw delivery) includes a "Topic" element.
Should
> >this not now
> >be a "Filter" element?
> >
> >
|