They are serializing the same object by using ObjectOutputStream theoretically
they should use the same number of bytes. It is just the underlying stream
which is different. One is Socket the other is ByteArrayOutputStream.
- bfn - JAW
---------- Original Message ----------------------------------
From: "Alan D. Cabrera" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Wed, 1 Sep 2004 12:20:11 -0400
>Interesting. It seems that you are comparing apples with oranges. What
>leads you to your expectation that those two methods from two different
>classes should return the same integer value?
>
>
>Regards,
>Alan
>
>> -----Original Message-----
>> From: John Woolsey [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, September 01, 2004 11:07 AM
>> To: [EMAIL PROTECTED]
>> Subject: RE: Socket Fun
>>
>> The mearsurement of the bytearrayoutputstream is bytearray.length
>> The other one is harder to come by. It is
>> Socket.getInputStream.available() I believe. I don't have the code
>> snippets here. Someone here suggested that it might be the EOF marker
>on
>> the output stream. I believe I closed the stream but I will have to
>check.
>>
>> - bfn - JAW
>>
>> ---------- Original Message ----------------------------------
>> From: Alan Cabrera <[EMAIL PROTECTED]>
>> Reply-To: [EMAIL PROTECTED]
>> Date: Wed, 01 Sep 2004 08:51:50 -0400
>>
>> >How do you perform your measurement? Can you provide a code
>snippet?
>> >
>> >> -----Original Message-----
>> >> From: John Woolsey [mailto:[EMAIL PROTECTED]
>> >> Sent: Wednesday, September 01, 2004 8:37 AM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: Re: Socket Fun
>> >>
>> >> Good idea but I am using different ObjectOutputStreams. The first
>one
>> >is
>> >> to a byte array and the other is to a Socket Stream. The difference
>is
>> >4
>> >> bytes 179 for the socket and 174. I am going to guess it is a
>length
>> >> variable that is added to the byte array stream. I have gone to
>> >> completely serializing outside the socket stream which works, but I
>> >> thought the difference was interesting and worth bringing up.
>> >>
>> >>
>> >> - bfn - JAW
>> >>
>> >> adam wrote:
>> >>
>> >> > Referencing by ObjectOutputStream. The second time you serialize
>> >the
>> >> > object out over the stream, ObjectOutputStream replaces it with a
>> >> > reference back to the one it just sent. In one of the older
>JVMs,
>> >> > this kept things that were serialized from being garbage
>collected,
>> >> > although that's been fixed now.
>> >> >
>> >> > Adam
>> >> >
>> >> > John Woolsey wrote:
>> >> >
>> >> >> I am working on my RMI implementation and I was using the
>> >> >> ObjectOutputStream. I made a function serialize that I used to
>find
>> >> >> the length of the outbound data. Then I wrote the same object to
>a
>> >> >> socket. The sizes where different ?!? Anyone have any idea why?
>> >> >>
>> >> >>
>> >> >> - thanx - JAW
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> >
>> >-----------------------------------------------------------------
>> > Visit our Internet site at http://www.reuters.com
>> >
>> >Get closer to the financial markets with Reuters Messaging - for more
>> >information and to register, visit http://www.reuters.com/messaging
>> >
>> >Any views expressed in this message are those of the individual
>> >sender, except where the sender specifically states them to be
>> >the views of Reuters Ltd.
>> >
>> >
>
>
>
