Dave Winer: So, is your brain
really hierarchic? Nope. Mine is definately
intertwingly. Regular expressions are filed under BOTH Perl
and Python. Can't find a screwdriver? Perhaps a butter
knife will do. I don't divide people up into east coast vs
west coast, or even blonde, brunette, and redheads... all I see is
the code. (multiple semi-obscure references in that last sentence).
Glen Daniels: Enable SOAP 1.2 webmethod feature. Use it
Call call = new
SOAPEnvelope env =
RESTful SOAP. +1.
Pearson: There's one thing I'd like to mention: the
importance that the method used doesn't require separate RSS feeds
to be generated for old and new locations.
To cope with existing aggregators that understand HTTP
redirects but not the new redirect semantics, we want to be able to
use an HTTP 301 redirect to point from the old to the new location.
However, this means that RSS fetched from both URLs will be
This makes perfect sense to me. HTTP 301 redirect is the
RESTful solution. Blog hosting services should offer
it. RSS aggregators should not only follow it, but follow the
instructions specified in RFC1945:
The requested resource has been assigned a new permanent URL
and any future references to this resource should be done
using that URL.
The problem? Some aggregators are not
currently layered properly to handle this. Dave
Winer indicates that Radio is one such aggregator at the
moment. I suspect that this problem is widespread.
Update: Dave Winer indicates
that he is testing a fix! Bravo!
The solution? The solution is
not to do something instead of an
HTTP redirect. If there is a desire to do something in
addition to an HTTP redirect, then any solution must deal
with constraint that a redirect happened "under the covers" and
that the feed the aggregator is actually reading is, in
fact, the desired target feed.
Udell seems to prefer one such solution. I describe how
it would work here.
Other solutions are possible.
My preference, however, would be to have HTTP 301
supported correctly on both the clients and servers.
Despite my pleas, the
number of subscribers to my
is actually increasing. I don't want to force when everybody
switches their subscriptions over to intertwingly,
but perhaps a little good old fashioned social engineering might
if adritemcache^.when > date.set(14,10,2002,0,0,0)
add ("<description><div style="color:#"
+ contrast + contrast + contrast + "">" +
add ("<description>" + adritemcache^.text +