My last couple of blogs have talked about
long polling and
Spring's DeferredResult technique and to demonstrate these concepts I've shoehorned the code from my
Producer Consumer project into a web application. Although the code demonstrates the points made by the blogs it does contain a large number of holes in its logic. Apart from the fact that in a real application you wouldn't use a simple
LinkedBlockingQueue, but would choose JMS or some other industrial strength messaging service, and the fact that only one user can get hold of the match updates, there's also the problem it spawns badly behaved threads that don't close down when the JVM terminates.
You may wonder why this should be a problem…
