Add connection between students, presenter, and central server. #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Connection is the class we will use for all communications, sendMessage and registerMessageListener are the two methods we will be using most frequently.
|
Awesome. What do I need to get done? On Saturday, April 26, 2014, Josh Terrell [email protected] wrote:
Michael J. Sevilla |
|
@mjsevilla If you are working on anything that needs to be transmitted to other students/presenter or something that needs to be received from other students/presenter, you'll probably care about what's gong on here. Otherwise. this shouldn't change anything for you |
This adds quite a lot of stuff needed for authenticating. The public API function, Connection.authenticate, is functional. There were several hurdles along the way. One noteable one is that wx must be called in it's own thread. Both wx and reactor are event loops that need their own thread. Long story short, reactor never calls the user's callbacks; reactor adds the callbacks to a stack which is then called by wx. TODO: add a timeout to connection that responds to the user after.. a sec or so if there is no response from the server. Right now it just keeps on waiting if the server doesn't respond. start the central server from main.py or move it next to main.py handle the other public connection functions I forgot about commiting last night, my bad. This should have been broken up into several commits.
To run the server from main.py, run `python main.py server`
If the authorization request takes longer than 3 seconds to get a response, just assume it's failed.
Calling conneciton.hostPresentation(classname, callback) will attempt to host a presentation for the given class calling the callback with a HostResponse when the server has replied. (either failure or success)
1) If reactor is still running a second after we asked it to close, just kill the process rather than hanging for (literally) about a minute. 2) don't raise an exception if the user attempts to send a message in CentralClient and the connection is down.. just call the callback saying that the conneciton is down.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connection is the class we will use for all communications,
sendMessage and registerMessageListener are the two methods we will be using
most frequently.
this is the beginning of large changes.. I'll be adding more commits as we go.
TODO: add manual timeout for pending message responses.