Hey there, I'm currently working on porting the safewith.me server to Node.js. Besides reaching JS-Nirvana and allowing safewith.me to potentially do all sort of nasty stuff, such as use openpgp.js on the server. I am finding that this allows me to consolidate the testing infrastructure, since qunit is available for both browser as well as node.
I'm just thinking out loud here... but it could also be useful for openpgp.js to modularize and start supporting node.js: 1. There is still a big "Todo" in the Makefile for "make test". Perhaps using node.js would ease the use of a continuous integration tool such as jenkins, since one would not have to spin up a DOM with Rhino in order to do automate unit tests in s shell script without a browser. 2. This would allow us to run the all tests automatically when commits are made to github, which would make it easier for newcomers to the project (such as me ;)) to be more confident when commiting patches, as they would be informed via email when their commit causes the tests to fail. 3. But probably the most important reason for doing this would be that we would open the project up to the ever growing community of node.js developers and potentially attract more people. I think this could also be a big chance for the project to be taken more seriously, as even the biggest sceptics of javascript cryptography would agree, that it would makes sense to have a fully compatible server/client OpenPGP solution with a single codebase. I will start to play around with the node.js/qunit/jenkins combo and see if it helps safewith.me. If the experiment proves successful, I would gladly try to do the same with openpgp.js. The main reason being, that safewith.mewould profit alot from having openpgp.js be node.js compatbile. I would love to hear your thoughts on this. Thanks Tankred
_______________________________________________ http://openpgpjs.org
