Re: Concurrent, persistent background process for a J2EE container
- From: Donkey Hottie <spam@xxxxxxxxxxxxxxxxx>
- Date: 29 Aug 2008 19:22:08 GMT
Mark Space <markspace@xxxxxxxxxxxxx> wrote in
news:g99hco$v60$1@xxxxxxxxxxxxxxxxxxxxxxxxx:
Donkey Hottie wrote:
We can't use java.util.logging for this. Boss wants "structured"
data, not flat text files.
So you know about XMLFormatter for logging, right? I'm curious: why
doesn't that work?
Nope. But you got me interested! Like I said, I'm no guru in Java EE.
It'd consider writing your formatted data to a socket, just on the
general principle that it might be more robust and more portable than
permanently wiring your logs to a database. However, you probably
know your requirements best. I do think writing to a socket would
obviate the need for any kind of multi-threading however.
Socket? But there always has to be an another thread or process in the
other end of the socket, no?
Socket programming is nothing new to me, 20+ years with C++ but J2EE
practices are new to me.
.
- References:
- Re: Concurrent, persistent background process for a J2EE container
- From: Mark Space
- Re: Concurrent, persistent background process for a J2EE container
- From: Donkey Hottie
- Re: Concurrent, persistent background process for a J2EE container
- Prev by Date: Re: Best practices for declared exceptions
- Next by Date: Re: JAR in a JAR?
- Previous by thread: Re: Concurrent, persistent background process for a J2EE container
- Next by thread: Re: Concurrent, persistent background process for a J2EE container
- Index(es):
Relevant Pages
|