[ale] write to stderr via javascript?

Richard Bronosky Richard at Bronosky.com
Thu Aug 6 14:58:52 EDT 2009


Are you wanting to do this for a group of testers with whom you can
collaborate, or do you want to do this for all including anonymous
users? At Yahoo! we tried to log all JS errors for all visitors with
all browsers on all platforms. Not an easy task, but we pulled it off
pretty effectively. We preferred to use hidden functionality built
into virtually any Yahoo! software you might install (browser toolbar,
Y! Chat, Y! Music, Y! Widget Engine, Y! Mail helper plugin, software
installs from ISP partners like AT&T,  SBC, Verzion, British Telecom,
etc.) but if none of those plugins could be detected it would try to
use JS to attach and image tag to the DOM whose src was
http:/blahblah/beacon.php?var1=value&var2=value&etc=etc And beacon.php
just logged $_GET to a file. We got excellent information about how
effective we were at our attempts to make JS cross-everything. This
allow us to create the YUI framework.

Anyway, my point is that it sounds like all you need is beaconing.
This is a common design pattern for web apps. Wrap all of your JS in
try...catch blocks and create a simple server side API for your catch
to talk to.

On Thu, Aug 6, 2009 at 2:14 PM, Geoffrey<lists at serioustechnology.com> wrote:
> Charles Brian Quinn wrote:
>> How about this:
>>
>> http://getfirebug.com/logging.html
>>
>> We use Firebug and this logging extensively when we develop Ruby on Rails apps.
>
> Thanks, I'll check it out.
>
>
> --
> Until later, Geoffrey
>
> Those who would give up essential Liberty, to purchase a little
> temporary Safety, deserve neither Liberty nor Safety.
>  - Benjamin Franklin
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>



-- 
.!# RichardBronosky #!.



More information about the Ale mailing list