Hacker News new | past | comments | ask | show | jobs | submit login

I think all those requests might become a problem. It would be relatively easy to buffer such logs, though.

Nice approach.




> I think all those requests might become a problem.

Well it depends, the request is "fire and forget" so it's really cheap, you don't care about it coming back (or even about it generating an error — though you definitely need to handle that if you hook into ajaxError[0] or you might get recursive reporting errors). And you could expect those errors to be rare enough that the "buffer" would fill slowly and the odd error push wouldn't be a big strain.

[0] hooking into ajaxError is pretty dangerous really, if the user's connection goes down for instance the user machine is instantly going to loop at high speed.


I meant expensive server-side. I would even like to run something like this in production.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: