Comet and Reverse Ajax
Category: Education (depraced!)
- views: 2 161
- date: 22 April 2011
- posted by: yahoocan
One of the most basic laws of a web application is that the client, not the server, must initiate any communication between the two. There are a number of common–use cases where, ideally, the server would like to talk to the client—dashboards and monitoring apps, chat rooms and other collaborations, and progress reports on long–running processes. Comet (a.k.a. Reverse Ajax) provides a mechanism for enabling this. Comet is moderately complex to implement. But this practical, hands–on book gets you going.
In Part 1 of this book, we start by examining the use cases, and look at the simple alternatives to Comet and how far they can satisfy your needs. In some situations, though, only Comet will do.
In Part 2, we demonstrate how to set up and run a Comet–based application.
With this book, be a part of the next generation, Ajax 2.0.
What you’ll learn
Find out what Comet is and the trouble with HTTP.
See how to achieve push, polling, piggy–backing, raw sockets, and more.
Explore some common use cases and a worked example on “magnetic poetry.”
Understand what some issues and techniques are including the two–request limit, pub–sub and server architectures, and continuations vs. native Comet.
Use implementations of Comet, including Cometd/Bayeaux, Reverse Ajax in DWR, and more.
Work through the final example using DWR Framework.
Who this book is for
This firstPress title is for Ajax developers who are intrigued by Comet/Reverse Ajax, key to the next generation Ajax 2.0.
We need your support!
Make a donation to help us stay online
Bitcoin (BTC)
bc1q08g9d22cxkawsjlf8etuek2pc9n2a3hs4cdrld
Bitcoin Cash (BCH)
qqvwexzhvgauxq2apgc4j0ewvcak6hh6lsnzmvtkem
Ethereum (ETH)
0xb55513D2c91A6e3c497621644ec99e206CDaf239
Litecoin (LTC)
ltc1qt6g2trfv9tjs4qj68sqc4uf0ukvc9jpnsyt59u
USDT (ERC20)
0xb55513D2c91A6e3c497621644ec99e206CDaf239
USDT (TRC20)
TYdPNrz7v1P9riWBWZ317oBgJueheGjATm
Information |
|||
 |
Users of GUESTS are not allowed to comment this publication. | ||