> I can't speak for Ceki, but here's my 2 cents. Some applications try > very hard to control the number of threads and other resources for > efficiency purposes. For example, application servers are usually > written in this way. In fact, the EJB specification prohibits EJB from > creating their own threads. So creating hidden threads inside the > logging library would not be "nice" to users working in this environment. I agree. However, the use of java.util.Timer will not resolve that (since it has a thread inner class itself). I think that in such cases, enterprise server specific appenders are in order... no?
>>> Ceki Gülcü wrote: >>>[] it is not good practice to hide threads within appenders. >> Walid Joseph Gedeon wrote: >> What is the reason bahind this? The thread used is a daemon thread, so >> it >> will not hang the system... is it because of using up an additional >> thread >> per instance? >> In all situations, a common timer can be used to which this appender >> would >> register for events. > Raymond DeCampo: > I can't speak for Ceki, but here's my 2 cents. Some applications try > very hard to control the number of threads and other resources for > efficiency purposes. For example, application servers are usually > written in this way. In fact, the EJB specification prohibits EJB from > creating their own threads. So creating hidden threads inside the > logging library would not be "nice" to users working in this environment. > > Ray --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
