You are certainly NOT alone in that feeling. There are some entertaining flame wars about the topic (on other lists and blogs) if you search for 'em. The approach does seem to work surprisingly well to solve certain problems. It also breaks badly on certain network configurations, and places unexpectedly high loads on others.
I would say that if an application can be designed without reliance on the Comet style, it probably should be -- for broadest compatibility and greatest simplicity. Still, people have brought sane use cases forward on the list -- e.g. pushing discrete updates from sensors to an HTTP-based client over a private network -- where the style would be a great fit, and it would be awesome if the Restlet API were flexible enough to support it cleanly when needed. - R On 2/6/08, Kyrre Kristiansen <[EMAIL PROTECTED]> wrote: > > I know this is probably the best place for this, but > am I the only one that thinks Comet is pushing the > limits of HTTP too far (no pun intended)?
