Re: [rest-discuss] Re: Summarization on notifications?
----- Original Message -----
From: "Paul Prescod" <paul@...>
> But at a deep level I hate the idea of inscrutable bytes arriving from
> some remote source without telling me WHY they are arriving or HOW I
> would stop them. That's why I wanted headers that would make the message
> self describing. You would just click (literally or metaphorically) on
> the "unsubscribe URI" and the messages would stop arriving....
I feel the same - but it is also possible that response codes to the notify
might be useful (404 not found).
But with some UI agent storing the notifications, it might be better to
'stop the noise now' via the URI in a header.
I like both approaches.
- It could be; however, for some applications, that's too limiting.
More to the point, it's difficult to arrange your resources so that
these relationships are meaningful in multiple contexts; e.g., P3P
and access control (insert your own, more notification-specific,
I discussed this a bit in Urispace . I'd approach the problem
On Fri, Feb 01, 2002 at 05:11:29PM -0800, S. Mike Dierken wrote:
> ----- Original Message -----
> From: "Mark Nottingham" <mnot@...>
> > A list of URIs is too limiting - it may not be practical or possible
> > to enumerate them all...
> That's just from Pauls example. However, is it a 'web collection' is the
> things inside aren't first-class resources (uri addressable)?
> > On Fri, Feb 01, 2002 at 09:19:25AM -0800, S. Mike Dierken wrote:
> > >
> > > ----- Original Message -----
> > > From: "Paul Prescod" <paul@...>
> > >
> > > >
> > > > I've clarified my thoughts on how to handle notifications for
> > > > collections. Collections are just documents that happen to contain
> > > > to other documents. Just hang a WATCH on that document.
> > > Woohoo! Yes, by george, you've got it! As a Groves dude, this should be
> > > pretty straightforward for you to work out the details of.
> > > And the resource (aka 'collection') may have metadata separate from the
> > > of URIs - how do distinguish between the two? That's where the
> > > comes from - they are 'updates' to the 'default collection' property.
> > > that is all really too complex for now - I can build it in the app layer
> > > with the low level primitives.
> > >
> > >
> > >