I agree that we would want to revisit the auto-update feature. The notion of an interval may be obsolete because the data would get "pushed" when the change occurs rather than polling for it.
That is the reason that NIO is required, so that the new Tomcat CometEvent classes can be used. They do not function with the standard HTTP connector. We could also implement websockets under Tomcat and gracefully fall back to long polling if the browser doesn't support them. Even IE does them as of IE9 so we wouldn't exactly be putting ourselves on the bleeding edge by supporting them. ----- "Jacques Le Roux" <jacques.le.r...@les7arts.com> wrote: > +1 for NIO > > It seems more than auto-update-interval and auto-update-target > attributes would be provided, Ean? > BTW it would be good if we added an example of use of > auto-update-interval and auto-update-target > > Also I stumbled upon this recently > http://www.w3schools.com/html/html5_serversentevents.asp unfortunately > only real browsers support it > > https://imgur.com/H4lcN ;) -- Ean Schuessler, CTO e...@brainfood.com 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com
