C like data structures in java ?

[ankitmcgill]

How do i read data from a socket and store it in some form of structure ?

for example: lets say the server A sends out in order

1. ID (int - 2 bytes)
2. Message corresponding to above ID (string - 12 bytes)

so the total size is 14 bytes.

So far from what i know i would have to do

read(2);
read(12) on the inputdatastream and store them in appropriate data types (int, byte[])

if i need to read this packet many times .. is there any way to make this easier ? like read the 14 bytes at once (into some custom object of my own - containing 2 data members) so that the values get automatically stored in the right fields...

something like

struct a
{
int id;
byte m=new byte[12]
}

socket_read(a);

print a.id;
print a.m;

thanks
-a

[Nicholas Jordan]

struct in Java is class very similar.

Socket is even a class, read docs on it.

[Norm]

so that the values get automatically stored in the right fields...

No way to redefine one long field with more than one short fields in java. You'll have to read the fields one by one and store their values where they go.

[ankitmcgill]

ok ... i started working on it and ran into some problems ...

the part that seems to be screwing up :

private int[] readSocket16(int length) throws IOException
{
int[] f=new int[length];
short[] t=new short[length];
for(int i=0;i<length;i++)
{

t[i]=input.readShort();
f[i]=(int)(t[i]&0xffff);
System.out.println(Integer.toHexString(f[i]));
}

}

what im doing here is reading a short(16 bits signed) and then storing it in an int to get unsigned effect. this does not seem to be working as when i do readSocket16(1) i should be getting value of 1152(0x0480) .. found this info by looking at the captured packet.

any ideas why its not working ?

-ankit

[Norm]

this does not seem to be working ...should be getting value of 1152(0x0480) .

What value are you getting?
What class is input?

[ankitmcgill]

im getting 0 ... output from the program

"Framebuffer width,height = 0,4"

the value after the "," is a similar call for another unsigned 16bit after the first one which should give 864(0x0360) ...

ankit

[Norm]

I do not understand your last post at all.

You show a String (in "s). How does that relate to the write statement that is sending the data that is read by the readShort method?
The value after the , looks like the string "height". How does that become x0360?

[ankitmcgill]

my bad .. let me explain it properly.

the actual call to print the output is :

System.out.println("Framebuffer width,height="+input.readSocket16(1)[0]+","+input.readSocket16(1)[0]);

the two calls to the function readSocket16(...) should return values 1152 and 864 but instead produce 0 and 4 respectively.


I checked the actual packet sent by the server using wireshark so i know the server is sending the right data ... its my program is srewing it up.

[ankitmcgill]

never mind ... took a break from the computer .. the mind was getting clogged up

replaced with a simpler function :

private int[] readSocket16(int length) throws IOException
    {
        int[] f=new int[length];
        char[] t=new char[length];
        for(int i=0;i<length;i++)
        {
            t[i]=input.readChar();
            System.out.println(t[i]);
            f[i]=t[i];
            System.out.println(f[i]);
        }
        return f;
    }

as for the weird output turns out there are some gaps in the protocol used by the server .. its sending some weird message out of queue ... cant explain it but its not my code for sure :D

[Nicholas Jordan]

the value after the "," is a similar call for another unsigned 16bit after the first one which should give 864

There are no unsigned anything in Java that I know of, nor void pointers - typing is just about everywhere. To see how Java does it ( extracting bits ) I suggest reading

${SOURCE_DIRECTORY}java\io\DataInputStream.java

for example:

    public final short readShort() throws IOException {
        int ch1 = in.read();
        int ch2 = in.read();
        if ((ch1 | ch2) < 0)
            throw new EOFException();
        return (short)((ch1 << 8) + (ch2 << 0));
    }

Note reading into an int and testing for EOF (-1), then extracting the short by casting. This is the way to Boogie with the Bean.

as for the weird output turns out there are some gaps in the protocol used by the server .. its sending some weird message out of queue

?

... cant explain it but its not my code for sure.

Write your own code?... that often seems to be the simplest way in Java.

[Norm]

protocol used by the server .. its sending some weird message out of queue .

How is the server formatting and sending what you expect to read as 1152 and 864? That will determine what you have to do to read it. What if it is sending characters (4 and then 3)? vs short (2 bytes) vs int (4 bytes) The receiving code has to know.