Should we also provide client and server logging? Is it worth?
Samual Harvey<br />SCJP2<br />SCJD2
Jim Bedenbaugh
Ranch Hand
Joined: Nov 09, 2001
Posts: 171
posted
0
Should we also provide client and server logging? Is it worth?
I wouldn't. It probably won't help your score and could possibly hurt it. Besides, a real logging implementation would involve using Log4J or something similar - well beyond the scope of this project.
Regards,
Jim
SCJP, SCJD, SCWCD, SCEA Part I
Samual Harvey
Ranch Hand
Joined: Aug 06, 2002
Posts: 119
posted
0
Guys do we have other ideas?
Michael Morris
Ranch Hand
Joined: Jan 30, 2002
Posts: 3451
posted
0
Hi Samual, I had logging on the server but not to a file. Most of the server GUI was a large text area that logged server actions, exceptions, clients connecting, etc. I considered putting a "Save log to file" on the File menu, but decided against it. Hope this helps, Michael Morris
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
Abhinav Anand
Ranch Hand
Joined: May 02, 2002
Posts: 113
posted
0
Hi guys, I have implemented logging of client activities on the server. All client activities like connecting, enquiry, add, modify, lock & unlock etc. are logged into a large text area. I have moved a step ahead by providing three different tabbed panes one to show all activities, another to show lock & unlock activities and another to show all exceptions thrown. I have implemented save server log and clear server log functionality. Note: It helped me a lot in debuggin my client. Hope this helps.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
