GoldSpike needs more eyeballs??”people looking at the code and contributing back
fixes. We would also appreciate people doing load testing and scalability tests to see where the
current project??™s reliability and robustness is.
JavaSand
JavaSand is a small piece of code that is a port of the project Sandbox. What made Sandbox
interesting for the regular Ruby distribution is that in most cases, you can??™t have more than
one Ruby interpreter per process. If you wanted to embed Ruby or just not handle communication
problems between processes, you were out of luck. Sandbox allows you to run several
Ruby instances within the same process, and also gives you capabilities to handle security in
a way that makes it safe to run any code you??™d like in it. The user of the Sandbox library can
describe which classes and operations should be available, and which shouldn??™t.
Because JRuby already provides for more than one runtime in the same process, Sandbox
isn??™t that important for JRuby from that perspective. On the other hand, providing the same
interface for creating more than one runtime, and also having the same interface for specifying
security constraints was useful, which is why I put together JavaSand. The code is small and
easy to understand, but uses many of the deeper features of the JRuby runtime to make everything
go smoothly. It??™s a useful project for some specific domains.
JParseTree
JParseTree is another port of a project that??™s useful in some circumstances, called ParseTree.
Pages:
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414