Jim says

The client/server code is fine.

I guess the protocol spec is the text that you have below? I don't think that this is specific enough - if that's what you were given and then asked to write a client/server app, you'd have lots of questions, like "what does 'proper message recieved' mean?".

I think we should have read some RFC's to see what protocol specs looked like.

Nate's Work

• First error check is to see if the server is responsive at all, closes the connection if no greeting is received.
• Next there's a call and response "confirmed" or "uncomfirmed" if the exact expected string isn't received
• First the server sends a message, the client respondes with either "confirmed" if the message is as expected or "uncomfirmed"
• A loop checks to see what is received on the server-side, if it's not "confirmed" then the message is sent again until "confirmed" is received
• This repeats until the proper message is recieved
• For the hit or stand section I didn't add in an extra confirmation loop as both sides are already checking the inputs and continuing to send on a 1 to 1 ratio until the proper input is found.
• I built a test server that allowed for custom responses and a test server that just didn't respond

Here's a sample test output with the custom server:

>>> python test_server.py
Socket successfully created
socket binded to 12345
socket is listening
what would you like your response to be?
why hello there
uncomfirmed
what would you like your response to be?
hello, let's play a game of blackjack
confirmed
what would you like your response to be?
got some cards for you
uncomfirmed
what would you like your response to be?
you were dealt the king of kinds and the queen of queens
confirmed
what would you like your response to be?
would you like to do some hitting or standing?
stand
what would you like your response to be?
you sure?
h
what would you like your response to be?
oh lets deal another card
s
what would you like your response to be?
sweet - dealer had way too many points - you win!

Here's a sample output from the client side with the non-responsive server:

>>> python client.py
server not responsive, closing connection
Traceback (most recent call last):
  File "client.py", line 27, in <module>
    s.send("uncomfirmed")
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 174, in _dummy
    raise error(EBADF, 'Bad file descriptor')
socket.error: [Errno 9] Bad file descriptor

Here's a sample functioning output with the main server:

>>> python client.py
hello, let's play a game of blackjack
you were dealt the 3 of Diamonds, and Ace of Diamonds, your score is 14
would you like to hit or stand? (h or s)
hit
please print a valid input, (h or s)
h
you were dealt the Jack of Clubs, your score is 24, would you like to hit or stand?
stand
please print a valid input, (h or s)
s
computer busted, player wins

• oops uploaded a few more files than necessary and forgot delete isn't working
• relevant files: server_thread.py, test_server.py, unresponsive_server.py, game.py

attachments

		last modified	size
	card.py	Mon May 06 2024 01:10 pm	2.1K
	client.py	Mon May 06 2024 01:10 pm	1.1K
	deck.py	Mon May 06 2024 01:10 pm	773B
	game.py	Mon May 06 2024 01:10 pm	4.3K
	hand.py	Mon May 06 2024 01:10 pm	980B
	server.py	Mon May 06 2024 01:10 pm	1.4K
	server_thread.py	Mon May 06 2024 01:10 pm	748B
	test_server.py	Mon May 06 2024 01:10 pm	795B
	unresponsive_server.py	Mon May 06 2024 01:10 pm	573B