The problem with logging for php apps is that it's just... dead
slow ... An error log is no problem (set_error_handler &
set_exception_handler are your friends to build that), but to really
'log' ... the amount of waiting between processes would quickly affect
the performance & scalability.
I've played with the idea of building a good but basic error logging
facility into shindig, but i'm also afraid it'll conflict with sites
that integrate shindig, and people are just used to normal php errors
in their browser window, so far i haven't dared to attempt it yet.
If you think such a thing should be put into shindig, i could whip one
up pretty quickly
-- Chris
On Jul 14, 2008, at 3:29 PM, Ropu wrote:
the php version right now, it doesnt...
but patches are more than welcome.
ropu
On Mon, Jul 14, 2008 at 10:11 AM, ajay singh <[EMAIL PROTECTED]
>
wrote:
Thanks Ropu
I was also using the Apache log.
Fire bug is a good option . i'll try that.
Is Shindig also maintain its log anywhere?
Thanks
Ajay
Ropu <[EMAIL PROTECTED]> wrote: Hi, my best suggestion is to
write to
the Apache (or web server) logs.
just #tail -f "WS_error_logs"
also i would suggest to work with Firebug to debug the HTTP
traffic...
ropu
On Mon, Jul 14, 2008 at 7:59 AM, ajay singh
wrote:
Hi
I am connecting shindig to my SNS backend data.
Now If any error occurs in my service files
(People,Activities,AppData),
then how to know this error?
Suppose i have done any syntax error in writing query in my
dbfetcher(
something like PartuzaDbFetcher) then how can i debug the error.
Thanks
Ajay
--
.-. --- .--. ..-
R o p u
--
.-. --- .--. ..-
R o p u
