Hi Anders,
At 10:37 08.06.2001 -0400, you wrote:
>An alternative to adding a version number to each serialized
>LoggingEvent, and thus sending it for each event, is to think of
>SocketAppender as using a protocol with a higher version number. The
>difference is that the version number (which would still signify the
>format of whatever is sent over the connection) is only sent to the
>server when the connection is established. At connection startup the
>client sends protocol name + version number -- much as in HTTP.
Good point.
>If the client appender was to send formatted logging entries as
>discussed recently, the protocol name would be different. This should
>make it a little bit easier for servers to support multiple different
>protocols. We still need to be careful with how LoggingEvent is
>modified, of course.
Agreed.
>BTW, isn't the class serialVersionUID already written as part of
>serialized objects?
I am sure it is. However, I don't know if it is available to the user. Cheers, Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
