Hi, I was wondering if the mywebpage.html file was able to be used as an interface for our project or if we were required to create one. Also, does each webpage need to only include options from all other stations or just the station that it is? My understanding is that, for each station, we need an html file that allows the user to input the destination, with its initial source being fixed to the one connected to the particular port. So, for example, if stationA was running on port 4001 and station B was running on port 4005, when you access localhost:4001 you will only be able to query for routes from stationA to any other station. Similarly, on localhost:4005 you will only be able to query for routes from stationB to any other station, and routes from stationA to other stations cannot be queried. Thank you

ANONYMOUS wrote: The requirements are that each server, which owns the timetable of a single station, has two open ports: - its TCP/IP port for communicating using HTML, typically between a web-browser or the command-line utility 'curl'. - its UDP/IP port used for communicating with other stations, using a protocol of your own design and implementation It does not matter if you use a single webpage for all stations (though you'll need to know all remote hostnames and their ports), or a single webpage per station. As with most web-based programs on the web, it'd be very 'standard' for each station to deliver its own query page in response to any query on its TCP/IP port. Hope this answers your question.

So, to confirm, we can use the mywebpage.html page provided and do not need to create our own to query info from the user? Do we just need to figure out how to establish a connection to obtain that information? Thanks again

ANONYMOUS wrote: You may use any other materials I've provided. Note, however, that mywebpage.html and/or the script that generated it, will require changing if you have different station names, and begin developing for multiple computers.