[retube]

Isn't this what Tapestry uses for client side error messaging? It's actually pretty useful for including in web-app frameworks: you can alert the developer to framework errors which might go un-noticed if just written to console.log. Of course you can disable in production.

On a side note, I've wondered how useful/practical server-side logging of js running client-side would be. For keeping track of what your users are doing, errors thrown etc.

[arethuza]

That's not a bad idea. Some suggestions/ideas:

- It would need to be asynchronous

- It would be nice to collect a log locally and send it centrally under specific circumstances (e.g. an error occurs send everything that has been logged so far)

- Using some kind of local storage option might be nice (e.g. the interface to SQLite that WebKit-based browsers have).

[retube]

It'd be fairly simple I think: a global object with .info(), .debug() etc methods. You'd have to make x-domain ajax calls to post back the message as the log server would have to run on another port. Various config options to change server, port, log-level defaults. And then a simple server to handle the posts and write out to log file on disk. You could even have a hosted/cloud service for those that didn't want to run their own logging server.

[retube]

ha - already exists: http://log4javascript.org/