Göran: Yesterday night we have a very good discussion about logging in IRC. I was asking about Logging in order to add log to SqueakDBX. I think there were some interesting questions:<br><br>1) Should a framework, like SqueakDBX, log? Or this is a responsibility of the "user" of the framework ?<br>
<br>Here, I will say: I think framework must log because it helps the framework team to find out bugs or give them information about it. I think this is something good. Obviously the framework should only log things related to the framework itself and not logic related with the user of it.<br>
<br>2) If so, should it be optional ?<br>I think i must. I mean, user can enable or disable it. <br><br>3) Suppose I want very much performance, and the user disable logging. Which is the best way of doing this?<br><br>4) No matter 1) to 3), framework's user can log. I mean, it can do something like [xxxx] on: DBXError do:[ self log 'something' ]<br>
<br>In fact, I decided (actually I must discuss with the team) to use Logging and SimpleLog in SqueakDBX.<br><br>Any opinion about this?<br> <br><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 8:21 AM, Göran Krampe <span dir="ltr"><<a href="mailto:goran@krampe.se">goran@krampe.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi!<br>
<br>
Mariano Martinez Peck wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
ok. If you say so, I will try it as soon as I have time and I will let you know my feedback and any question I have with it.<br>
</blockquote>
<br>
I recommend (of course) using "SimpleLog", and optionally with the<br>
"Logging" frontend from Keith.<br>
<br>
SimpleLog was developed in the Gjallar project and it has the following<br>
goodness:<br>
<br>
- Simple. :)<br>
- Uses the standard syslog levels.<br>
- Has a UDP based syslog backend. Fast and very useful.<br>
- Has a Morphic viewer which is quite nice and has filtering abilities.<br>
- Has log file rotation.<br>
- Can still log to Transcript but it is protected by a mutex.<br>
<br>
If you need to use external monitoring/alarm tools and/or suddenly need<br>
to deploy an app "clustered" then the syslog backend is very nice to<br>
have. Otherwise you end up with one log file per "clustered image" which<br>
is not so nice.<br>
<br>
If you use the "Logging" frontend (which I haven't used myself) then you<br>
of course have options to choose backends.<br>
<br>
regards, Göran<br>
<br>
<br>
</blockquote></div><br>