Hi Mike,
I'm also leaning towards Ceki's and Mike's suggestion. By ensuring the v_n
data gets serialized before v_n+1, one should at least be able to upgrade
log4j on the downstream log4j servers without affecting the upstream
application servers (log4j clients).
As for the XML solution, perhaps this can be provided as an alternative.
There is concern here about performance and I share that concern. But
there are some who seem interested in this for the benefits one gets in
exchange. Someone a short while back shared a text socket appender they
wrote. Perhaps an XML socket appender could be developed that converts a
logging event into some agreed upon XML format.
- Paul
Paul Glezen
IT Specialist
Software Services
818 539 3321
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
