🚀 go-pugleaf

Paul,

I hope you haven't forgotten that UDP doesn't guarantee delivery of
packets to their destination nor does it even guarantee that the
sequence of received packets will be correct.  Maybe that's why your
objects are corrupted when they get read in?  I don't know much about
broadcasting, but maybe you should consider using TCP instead of UDP?

Ed

Paul Hussein wrote:
> 
> I am currently trying to provide a generic class that will establish an
> UDP/IP Broadcast connection and broadcast datagrams.
> 
> The UDP/IP stuff is fine. However, I would like to be able to take a
> java.lang.Object ( or an instance of a class that is inherited from it ) and
> convert it into bytes in an automatic manner.
> 
> I've tried to use streams, creating my own UDPBroadcastInput and Output
> streams, but when I use the ObjectInputStream stream reader and writer the
> app complains about the stream being corrupt when it tries to read from it.
> I believe this is due to the version number being passed out from the
> ObjectInputStream  and ObjectOutputStream . Does anyone know of any way to
> get round this. Alternatively is there a way of accessing serialization
> without using these classes so that I can manipulate the stream of bytes
> directly.
> 
> I could always try to assign the object to an array of bytes as I would in
> C, however I would need to know the size of the java.lang.Object and its
> descendants. Is there a way of finding out ???
> 
> Any help would be very much appreciated
> 
> Cheers