EnterpriseQualityCoding / FizzBuzzEnterpriseEdition

FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
21.46k stars 758 forks source link

Printing should be async #151

Open runesl opened 10 years ago

runesl commented 10 years ago

We never want to block on IO operations, so all prints should be async. This can be done by making the print-methods return Future and start an async print-thread using Threads from a thread-pool. Obviously, thread management code must be included to monitor and handle all possible and impossible outcomes of PrintOperation including timeout.

vladd commented 9 years ago

Don't forget the cancellation possibility! We don't want to wait for the output if this task takes too long and we want to switch to the next one. Of course, the cancellation granularity (single line? single character?) must be configurable via XML. As well, we should think about output progress reporting.

filipvanlaenen commented 9 years ago

This is a good issue to introduce a queue.

Dmitry-Me commented 9 years ago

@filipvanlaenen Maybe it's even time to invent a hash queue.

beresfordt commented 8 years ago

@Dmitry-Me I think that we should look at an enterprise ready queueing solution for which we can get a solid support contract in place; WebsphereMQ immediately springs to mind