Future of Web Apps (FOWA)
Note by Phil Wilson:
mentions the recent "arguments" with fielding on their blogs.
history of physics etc.
overview of the history of the web and REST.
"there are some fundamental problems with the way we construct HTTP" (construct or use?)
polling is lots of wasted time and effort on both the user and server side.
applications versus static information delivery. it's the queuing messages system versus document delivery isn't it? (pull vs push)
this pretty much an introduction to jabber, what it is, how it works and why, for certain purposes is better than HTTP.
draw parallels between HTTP and XMPP, code comparisons
hops across the atlantic are fast, again with IO vs. CPU consumption and processing.
Friendfeed SUP
XMPP for delivery of information when it changes rather than constant polling, example with fireeagle.
bit or a disorganised talk, not as compelling as the earlier one
history of physics etc.
overview of the history of the web and REST.
"there are some fundamental problems with the way we construct HTTP" (construct or use?)
polling is lots of wasted time and effort on both the user and server side.
applications versus static information delivery. it's the queuing messages system versus document delivery isn't it? (pull vs push)
this pretty much an introduction to jabber, what it is, how it works and why, for certain purposes is better than HTTP.
draw parallels between HTTP and XMPP, code comparisons
hops across the atlantic are fast, again with IO vs. CPU consumption and processing.
Friendfeed SUP
XMPP for delivery of information when it changes rather than constant polling, example with fireeagle.
bit or a disorganised talk, not as compelling as the earlier one
