ANONYMOUS wrote: The project requires two or more programs to communicate across a network. If all goes well - great! - and the successes will be the correct/meaningful results. But a number of things can go wrong - network messages not delivered, invalid requests misunderstood, an incorrect algorithm to answer queries, an incorrect implementation of even a working algorithm, there not being a solution to a query within the data (the timetables) - all very 'standard' problems for any software project. Your project should anticipate and detect these errors and report them 'back' to who/whatever made the original request (here, via a web-browser).