Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (754)
Games in Android Showcase (229)
games submitted by our members
Games in WIP (842)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  Strange problem with Objects streams  (Read 1581 times)
0 Members and 1 Guest are viewing this topic.
Offline tufflax

Junior Newbie

« Posted 2006-06-11 12:38:42 »


I'm writing a little multiplayer game and it goes kind of well. But right now I'm having a problem. The problem is that when I'm using ObjectInputStream/OutputStream the Objects are not transfered correctly...

I want to send a "ToServerPacket" to the server from the client. The ToServerPacket has only one instance variable (right now); a Position. The Position is a very simple class. It has only short x; and short y; and get/set methods. The ToServerPacket has a toString() which returns a String with the x and y values shown. Both ToServerPacket and Position implement Serializable.

What happends is that when I send a ToServerPacket, I receive a ToServerPacket on the other side, so far so good, but the values (x and y in the Position) are not correct! Whatever Position I send, I get x==0 and y==0 when I read them on the other side.

The way I tryed it was like this:
ToServerPacket p = new ToServerPacket(...);


Object o = in.readObject();

The toString() works but as I said the values after I read are always 0 and 0.

Bummer... Sad

Edit: It appears that the values are not always 0 and 0, but instead equal to the values in the very first packet that was sent.

Some code:
Online CommanderKeith
« Reply #1 - Posted 2006-06-11 13:16:45 »

This is the mystifying problem everyone using ObjectIn/OutputStreams has to have.  And after all of the pain trying to figure out what's wrong, you'll never forget the solution.  What is happening is that after the first write, all writes to that same object are sent as a reference only even though you changed the original object. 

After out.writeObject(p) call out.reset() and it will be apples.   Wink

Good luck.

1.  you can send a new object each time, but that's messy since any Object fields of that new Object need to be new as well, etc. 
2.  create a new ObjectOutputStream for each new send, but make sure you create a new ObjectInputStream to recieve it as well, there must be this symmetry.  This makes more work for the Garbage COllector though & each write(obj) will produce more bytes than by having a single stream that's re-used.
You're better off overall by just calling reset().  Smiley  )

Pages: [1]
  ignore  |  Print  

DesertCoockie (33 views)
2018-05-13 18:23:11

nelsongames (75 views)
2018-04-24 18:15:36

nelsongames (70 views)
2018-04-24 18:14:32

ivj94 (752 views)
2018-03-24 14:47:39

ivj94 (82 views)
2018-03-24 14:46:31

ivj94 (622 views)
2018-03-24 14:43:53

Solater (98 views)
2018-03-17 05:04:08

nelsongames (179 views)
2018-03-05 17:56:34

Gornova (405 views)
2018-03-02 22:15:33

buddyBro (1065 views)
2018-02-28 16:59:18
Java Gaming Resources
by philfrei
2017-12-05 19:38:37

Java Gaming Resources
by philfrei
2017-12-05 19:37:39

Java Gaming Resources
by philfrei
2017-12-05 19:36:10

Java Gaming Resources
by philfrei
2017-12-05 19:33:10

List of Learning Resources
by elect
2017-03-13 14:05:44

List of Learning Resources
by elect
2017-03-13 14:04:45

SF/X Libraries
by philfrei
2017-03-02 08:45:19

SF/X Libraries
by philfrei
2017-03-02 08:44:05 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!