Use file level custom logging instead of event-log based logging

[GoogleCodeExporter]

There has been certain issues with the way logging have been implemented in
Google Services for SharePoint:

1. Non-admin users having only read permission is not able to write into
the event log.

2. Logging can not be made verbose as event-log is common to all
applications and should not be extensively used.

3. Difficult to get logs from customers in case of debugging.

Using a third party logging utility will require extra libraries to be
shipped with the connector.

We can make use of file based custom logging.

Original issue reported on code.google.com by th.nitendra on 23 Nov 2009 at 3:23

[GoogleCodeExporter]

Because with certain issues with both - Event-Level logging and File based 
custom
logging - it has been decided not to log anything at SharePoint server end. 
Rather,
all the log messages are forwarded to the connector with SOAP response and are 
logged
into the connector logs.

Following were the promary issues with the earlier approaches:
Event Log based logging - Every user might not have permission to write into 
event logs.
File based custom logging - Two processes may simultaneously try to write into 
the
log. Only one would get the handle. A typical synchronization issue; difficult 
to
handle in case of web service.

Original comment by th.nitendra on 25 Nov 2009 at 5:28

• Changed state: Fixed

[GoogleCodeExporter]

Verified in 2.4 Release

Original comment by ashwinip...@gmail.com on 14 Dec 2009 at 6:43

• Changed state: Verified