Lists Home |
Date Index |
He didn't say it wasn't possible, just that
it isn't HTTP. I think he meant, if you need
to push, there are better ways to do it.
Umm... Daniel said something to Al about
being "the last UDP holdout" or somesuch.
It just ain't so. Lotsa protocols, some
better suited for some things than others.
HTTP seems to be the most mediocre and
for some reason, people like that, probably
the same people who like The Eagles.
Quake players think they are on The Web.
So do a lot of the marketing companies,
the investors, and so on, in fact, that
was the stampede we just saw vanish into
the Death Valley of IPOs taking a lot
of people's retirement funds and jobs
with them. "Adios! Happy Trails! So sorry,
gotta get to Club Med before the season
is over. You believed it; you lose!
Do your Due Diligence next time!"
So, URIs are The Web? Great. The W3C and
the TAG are done, unnecessary, finis, free
to go home and play with their babies. The
Web is at it's fullllllllllll potential.
There Ain't No The Web. Just parts and
From: Paul Prescod [mailto:firstname.lastname@example.org]
I don't have time to get into a protocol re-engineering session but it
is simply untrue that it is impossible to push information to multiple
places using HTTP.
> ... BTW: reliability is not simply
> about delivering packets but sometimes
> about getting them there on time, so what
> Al was saying is relevant if it affects the
> ability of the push dispatch to get the
> right messages to the right places on time.
Anyhow, nobody considers HTTP a replacement for UDP.
> VRML multicasting struggled with this mightily.
> How many real-time 3D gamers use HTTP, or the
> DIS simulations? Are they "off the web"?
Quake players think that they are surfing the web? I don't think so. If
you aren't using URIs then you aren't using the Web. If you're using
URIs but in a protocol that makes it hard or impossible to resolve them
then you're using the Web but not to its potential. The same goes if
you're using URIs but also using a bunch of private naming conventions
in method names.