Re: client server - client problem
I'm still curious about my earlier questions:
... you are doing the "writeObject()" call only to the client that sent the object.
Where is the code that would send it to another client?
Where is the code that even recognizes the [other] client?
Not that it matters, but it piques my curiosity: why did you keep Sun's names for the server classes?
You did put them in named packages, right?
I assume that the two questions you have asked is a solution to my
problem. Since I know the path therefore I will work out the solution.
I'm not sure how you could have concluded that, or why you would assume it
against the evidence. To begin with, I asked four questions, not two.
1. Where is the code that would send it to another client?
2. Where is the code that even recognizes the [other] client?
3. Not that it matters, but it piques my curiosity:
why did you keep Sun's names for the server classes?
4. You did put them [the Knock-Knock classes] in named packages, right?
Second, people usually ask questions because they want answers. Third, I
said, "I'm still curious".
It is, of course, your right not to answer, but it seems strange. Especially
so because you come here asking for help, but won't contribute to the
conversation when people ask you questions in return. You also didn't respond
to certain earlier questions or advice, such as to remove work from the class
I'm going to guess that the answers to #1 and #2 were, "There isn't any and
there isn't any, and gosh, that's where the problem lies (in part)." I'm
going to suggest that the answer to #4 should be, "Yes." As to #3, as I said,
it doesn't really matter.
Good luck in your future endeavors.