https://bz.apache.org/bugzilla/show_bug.cgi?id=58520
--- Comment #2 from Tweemaal Drie <jeperjaperjie...@gmail.com> --- Hi Mark, I meant indeed the isDone() operation on the Future. I agree it is a good thing seen from perspective of the server. However, from perspective of the client, once the client reconnects, it gets overloaded with events. The problem is that when processing event N, he has no idea that event N+1 is still in the pipeline, which means that event N can be discarded. How would one cope with this situation, in general? We could add a timestamp to the events, so clients can filter on that, which reduces the processing overhead. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
