Re: [syndication] Re: SOAP meets RSS

["Dave Winer" <dave@userland.com>]

Aaron, I just read the page carefully, and think I understand what's going
on. What's missing is what we provide in the <cloud> element, a way of
bridging RSS to the method being used.

Now I'll tread on thin ice, please correct me if I get this wrong.. This is
what the <cloud> element would look like if http-post were a supported
protocol.

<cloud domain="my.theinfo.org" port="80" path="/changed/email/"
registerProcedure="" protocol="http=post"/>

It would be noted that for http-post the registerProcedure attribute is
ignored.

Does that make sense? If so, I'll speculate on a next step. Do at least one
channel and a corresponding cloud that supports this protocol and then we
can see about connecting our systems. My philosophy on formats is that you
must do an implementation before documenting a protocol, so many glitches
and inadequacies are uncovered when doing an implementation, I don't trust
specs that haven't been fully implemented.

Dave


----- Original Message -----
From: "Aaron Swartz" <aswartz@swartzfam.com>
To: <syndication@egroups.com>
Sent: Saturday, January 06, 2001 10:38 PM
Subject: [syndication] Re: SOAP meets RSS


> dave@userland.com <dave@userland.com> wrote:
>
> > Notification makes it possible to always be current yet conserve
> > bandwidth and server cycles.
>
> Dave, this seems a lot like the changedPage spec which I've had out for
> months. Perhaps we can figure out a way for our systems to work together?
>
> http://my.theinfo.org/changed/
>
> A protocol="http post" or protocol="changedPage" addition to the <cloud>
> element would do quite nicely, I would think.
>
> --
> [ Aaron Swartz | me@aaronsw.com | http://www.aaronsw.com ]
>
>
>
>