help3002

It's UWAweek 20 (1st semester, week 11)

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!" followup message. How do I ask a good question?

Chris is away until 4th June. Dr Atif Mansoor is the unit's coordinator until then.

Displaying the 4 articles in this topic

Showing 4 of 446 articles.
Currently no other people reading this forum.

UWA week 19 (1st semester, week 10) ↓

project Did the one station know the name of all station (all 4)

4:15pm Tue 7th May, Jiayi C.

Hi I want to Know whether is allow one station know the every station name(don't know the localtion, don'tknow the timetable, just name), to insure the station check the validity of input.

project Did the one station know the name of all station (all 4)

4:32am Wed 8th May, Christopher M.

"Jiayi Cheng" <22*3*6*7@s*u*e*t*u*a*e*u*a*> wrote:

> I want to Know whether is allow one station know the every station name(don't know the localtion, don'tknow the timetable, just name), to insure the station check the validity of input.

(coincidentally, this was discussed in a tutorial, yesterday) Stations should not know (or need) the names of all other stations when sending out their queries, other than when identifying a particular destination. But it is reasonable for each station to know other stations' names if they are being presented on the 'front' webpage of any station-server, so that the user can indicate their required destination. This is far better than having the user type in, and misspell, a station name. There's two simple ways to create and display that webpage: - either manually into a file, and have the station-server just deliver that file's contents, or - have the station-server read station name from a file, each time. You can collate all station names, simply, from the names of timetable files: ls tt-* | cut -c4- > ALLSTATIONS

UWA week 20 (1st semester, week 11) ↓

project Did the one station know the name of all station (all 4)

12:25am Mon 13th May, Henry H.

Hi Chris, So I just want to clarify that this means it's not our protocol's responsibility to try & collate + maintain a list of all available stations in each station, but rather to gleam this from the timetable files in the project? Because we're not sure what that file structure will be like when you mark, so I'm assuming you want us to scan every file in the server's directory for any that start with 'tt-' and then add the rest of the file's name (the station name) to this list for the server to share as the list of possible destinations?

project Did the one station know the name of all station (all 4)

8:02am Mon 13th May, Christopher M.

"Henry Hewgill" <23*1*7*8@s*u*e*t*u*a*e*u*a*> wrote:

> So I just want to clarify that this means it's not our protocol's responsibility to try & collate + maintain a list of all available stations in each station, but rather to gleam this from the timetable files in the project? Because we're not sure what that file structure will be like when you mark, so I'm assuming you want us to scan every file in the server's directory for any that start with 'tt-' and then add the rest of the file's name (the station name) to this list for the server to share as the list of possible destinations?

Hi Henry, There's no requirement for your protocol to find all station names, and no station should need to know/use all other station names in your protocol. But see [help3002]⬈ Each station only needs to have and read its own timetable file; it's reasonable to assume it's in the same directory as your station's executables. There's no need to scan the directory for *your* timetable file, and you won't be reading other timetable files.