execution-time efficient osgi-logging. LogService vs. classic logging interfaces

[Roland <wg...@ids.de>]

Hello everyone,

I created my own LogService-Bundle and I'm asking me if it is execution-time
efficient to do so. This question arises because at any time the service can
be stopped and I have to take care that all references are released and
synchronized at runtime. This can be much execution-time consuming.

        synchronized(logservice){
          if(logservice != null){
            logservice.log(...);
          }
        }

Have some Felix-User experiences in that topic? How do you log in a mobile
device / embedded system?

additional informations...
http://ekkescorner.wordpress.com/2009/09/03/osgi-logging-part-2-logservices-vs-classic-logger/



--
View this message in context: http://apache-felix.18485.x6.nabble.com/execution-time-efficient-osgi-logging-LogService-vs-classic-logging-interfaces-tp5004135.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org