that's pretty cool. amazon could resell your free browser cycles.
I've been saying for a while that I'm surprised no-one has written a BitCoin miner in JS and started pushing it out to connecting browsers. Given how much time a pop-under advert can sit no someone's machine before they notice it could be relatively lucrative. You'd not get a lot of processing per client per block of time even with the best current JS JIT compilers (especially as GPU mining is where it is at now), bu…
Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
11–20 of 21 posts
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#12that's pretty cool. amazon could resell your free browser cycles.
I've been saying for a while that I'm surprised no-one has written a BitCoin miner in JS and started pushing it out to connecting browsers. Given how much time a pop-under advert can sit no someone's machine before they notice it could be relatively lucrative. You'd not get a lot of processing per client per block of time even with the best current JS JIT compilers (especially as GPU mining is where it is at now), bu…
https://bitcointalk.org/index.php?topic=9042.msg130817#msg13...
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#13The problem we (the YUI project) ran into was test failures that would occur only within iframes. We found lots of iframe-only quirks that were useful to know about, but were also distracting since we wanted to make sure using YUI in a typical browser context works first. (I've talked to jQuery's TestSwarm maintainer and they've had similar problems with iframes.)
The tool we use, Yeti, was since rewritten to not require an iframe. http://yeti.cx
I continue to work on Yeti, and there's a lot of interesting things we have done (using multiple browser instances to speed up testing, launching browsers automatically, CI integration) and hope to do (code coverage, performance measurements). Help wanted!
It's neat to see this kind of thing become more popular, and I hope these projects can make testing easier for everyone.
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#14Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#15that's pretty cool. amazon could resell your free browser cycles.
http://news.ycombinator.com/item?id=347359
Plura ran into trouble because they built a pay-for-grid computing platform where the nodes were unsuspecting users:
http://pluraprocessing.wordpress.com/2009/08/24/our-response...
Personally I'd like to see a SETI@Home or Folding@Home in the browser first.
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#16Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#17A couple years ago, I used Node.js to build a tool that would run tests in iframes. It's similar to the OP's tool Thrill, but mine was a lot simpler. http://thrilljs.com The problem we (the YUI project) ran into was test failures that would occur only within iframes. We found lots of iframe-only quirks that were useful to know about, but were also distracting since we wanted to make sure using YUI in a typical browse…
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#18The possibilities are interesting, what will you use it for?
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#19Very similar conceptually to a tool (Attester) that our team has released a couple of months ago. https://github.com/ariatemplates/attester/ We use it as a distributed way to perform tests in our main project (Aria Templates: https://github.com/ariatemplates/ariatemplates ). The tool is able to use PhantomJS (configurable number of instances) and "normal" browsers which can connect in the same manner (by opening a UR…
Re: Queen – A Framework To Run Scripts On Many Remote Browsers Using Node.js
#20that's pretty cool. amazon could resell your free browser cycles.