ANONYMOUS wrote Glad that something's working for you, though I can see how allowing the select() call to unblock after 10sec would help the datagrams arrive. It sounds like you don't have all the important descriptors set in your readset .

Yeah, my code is near identical to that format and it was not working, I added a timeout into the select() of 10s and now it gets the neighbours every time (with almost no change to the actual time to get all the names - near instant)

Is it possible to release a demo testing thing similar to the "myscheduler" testing which was set up, but for this project. When determining valid paths especially on large networks of 20 or more stations it becomes very difficult to determine if a p...

Further to this question, are we permitted to use Python's asyncio module to prevent thread blocking when handling network communication?

My current implementation blocks new udp connections while waiting for acknowledgements from neighbouring hosts to come back for a specific frame. this will slow down response time, will this get marked down?

Sorry, forgot to add - I don't use the station names for anything, other than naming the final destination station, and to help with debug printing.

ANONYMOUS wrote I appreciate that no-one likes the phrase, but "it works for me" create bind to your TCP and UDP sockets sleep(2) transmit a 'hello' datagram to your neighbours enter your select() loop ..... receive 'hello' datagr...

Hmm, I tried that and it didn t seem to work

ANONYMOUS wrote One possibility - if you're starting all of your station servers from a script then, when one of them transmits that first 'hello' datagram, its destination server might not have started yet. The datagram is transmitted, but there's n...

I'm attempting to do this exact thing where as the station starts up it sends its name to all its neighbours (before any requests are made), then in the main server loop with select() each station picks up on neighboring station's names. But for me I...

ANONYMOUS wrote Not permitted, because it's not what is specified on the project sheet, and will prevent your project from being tested using some common scripts. It's trivial to first send a datagram to each of your neighbours, telling them your name....

Can we pass on the names of the neighbours in command line along with the IP port or is this not allowed

ANONYMOUS wrote Ouch I've cut-and-paste that bit from another recent project (and it's been proofread 'a million' times), but you're the first to find that error (thank you ). It now correctly states "You must clearly describe your design choices, ...

ANONYMOUS wrote You're writing two servers, one in language L1 and the other in language L2. Instances of the server written in L1 should be able to communicate with servers written in L2. As they need to communicate using (your) common protocol, they'...

ANONYMOUS wrote There's a past discussion on this here https secure.csse.uwa.edu.au run help3002?p np opt U309 The unreliability of UDP needs to be addressed so that any lost datagrams do not prevent a query being answered. The use of sequence numb...

Hi Jasper, Yes, this is permitted within our scope, but I can't immediately see any advantage to it. If a datagram is sent from temporary socket, with a randomly assigned port, then the station receiving that datagram doesn't know which station sent it...

Hi chris, we almost finish our project now, but you metioned "identify what is being protected by your system, how that protection is provided, and identify any known weaknesses with your approach or its implementation" But nothing was pointed out i...

Does the python and c server implementations have to cross communicate with each other or is it two seperate servers but must perform identically?

does "handle any issues which occur with the unreliable UDP" mean doing something such as putting sequence numbers in the packets?

Hi Chris, I have seen some examples online and some students who create a new temporary UDP socket whenever a server wants to make a request to another server. The socket is not bound to another port number, it is left to the OS to bind the port to an...