Trying to send multiple types in a byte array -- questions?

Question

Hi,
I have a question which I would really appreciate any help on.
I am trying to send a byte array, that contains multiple types using a UDP app. and then receive it on the other end.
So far I have been able to do this using the following code. Please note that I create a new String, Float or Double object to be able to correctly send and receive. Here is the code:
//this is on the client side...
String mymessage ="Here is your stuff from your client" ;
int nbr = 22; Double nbr2 = new Double(1232.11223);
Float nbr3 = new Float(8098098.809808);
ByteArrayOutputStream baos = new ByteArrayOutputStream();
ObjectOutputStream oos = new ObjectOutputStream(baos);
oos.writeObject(mymessage);
oos.writeInt(nbr);
oos.writeObject(nbr2);
oos.writeObject(nbr3);
oos.close();
byte[] buffer = baos.toByteArray();
socket.send(packet);
//this is on the server side...
byte [] buffer = new byte [5000];
String mymessage = null; int nbr = 0; Double nbr2 = null;
Float nbr3 = null;
mymessage = (String)ois.readObject();
nbr = ois.readInt();
nbr2 = (Double) ois.readObject();
nbr3 = (Float) ois.readObject();
My main question here is that I have to create a new Float and Double object to be able to send and receive this byte array correctly. However, I would like to be able to have to only create 1object, stuff it with the String, int, Float and Double, send it and then correctly receive it on the other end.
So I tried creating another class, and then creating an obj of this class and stuffing it with the 4 types:
public class O_struct{
//the indiv. objects to be sent...
public String mymessage; public int nbr; public Double nbr2;
public Float nbr3;
//construct...
public O_struct(String mymessage_c, int nbr_c, double nbr2_c, float nbr3_c){
my_message = my_message_c;
nbr = nbr_c;
nbr2 = new Double(nbr2_c);
nbr3 = new Float(nbr3_c);
Then in main, using this new class:
in main():
O_struct some_obj_client = new O_struct("Here is your stuff from your client", 22, 1232.1234, 890980980.798);
oos.writeObject(some_obj_client);
oos.close();
send code....according to UDP
However on the receiving side, I am not sure how to be able to correctly retrieve the 4 types. Before I was explicitely creating those objects for sending, then I was casting them again on the receiving side to retrieve then and it does work.
But if I create a O_struct object and cast it as I did before with the indiv objects on the receiving end, I can't get the correct retrievals.
My code, on the server side:
O_struct some_obj_server = new O_struct(null, null, null. null);
some_obj_server = (O_struct)ois.readObject();
My main goal is to be able to send 4 types in a byte array, but the way I have written this code, I have to create a Float and Double obj to be able to send and receive correctly. I would rather not have to directly create these objects, but instead be able to stuff all 4 types into a byte array and then send it and correctly be able to retrieve all the info on the receiver's side.
I might be making this more complicated than needed, but this was the only way I could figure out how to do this and any help will be greatly appreciated.
If there an easier way to do I certainly will appreciate that advise as well.
Thanks.

Answer 1

public class O_struct implements Serializable {
// writing
ObjectOutputStream oos = ...;
O_struct struct = ...;
oos.writeObject(struct);
// reading
ObjectInputStream ois = ...;
O_struct struct = (O_struct)ois.readObject();
I will be sending 1000s of these byte arrays, and I'm sure having to create a new Double or Float on both ends will hinder this.
I am worried that having to create new objs every time it is sending a byte array will affect my application.
That's the wrong way to approach this. You're talking about adding complexity to your code and fuglifying it because you think it might improve performance. But you don't know if it will, or by how much, or even if it needs to be improved.
Personally, I'd guess that the I/O will have a much bigger affect on performance than object creation (which, contrary to popular belief, is generally quite fast now: http://www-128.ibm.com/developerworks/java/library/j-jtp01274.html)
If you think object creation is going to be a problem, then before you go and cock up your real code to work around it, create some tests that measure how fast it is one way vs. the other. Then only use the cock-up if the normal, easier to write and maintain way is too slow AND the cock-up is significantly faster.