Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am programming a networked turn based java game, and use the java serialization api to serialize the game state each time a player does a move.
To my annoyance, I discovered that the api assumes the objects are immutable. This means that each time I try to send the updated game state, the old game state is received at the clients.
Is there some way to make the objectoutput/objectinputstream forget that an object has already been sent and make a new object each time?
ObjectOutputStream.reset() is what you are looking for: Oracle docs. It forces the stream to send updated objects.