Hopbot log for 2009-04-03 - Helma IRC channel: #helma on irc.freenode.net

2009-04-03:

[10:19] <hannesw> Just committed sandbox support to helma-ng.
[10:20] <hannesw> helma> var sandbox = createSandbox('modules/sandbox', {require: require});
[10:20] <hannesw> helma> sandbox.runScript("test.js");
[10:21] <hannesw> http://dev.helma.org/trac/helma/browser/helma-ng/trunk/modules/helma/system.js?rev=9571#L29
[10:22] <hannesw> of course you can still escape the module root using "..", but that's a different problem :-)
[17:06] <decke> i initialize an java object in Global.onStart() and save it in app.data.something but it looks like helma does that per Thread so i end up having many of that objects but only want one - is there a way to tell helma that this object is threadsafe and share it over his threads?
[17:17] <decke> the java keyword for such a thing would be static..
[21:03] <zumbrunn> decke: I'm surprised that's not thread safe
[21:03] <zumbrunn> does it work as expected if you do set the object later on?
[21:04] <zumbrunn> like if you chek for it in onRequest and set it if it doesn't exist yet?
[21:04] <decke> zumbrunn: i could test it in an seperate app but it looks like helma has created several objects for it...
[21:05] <decke> haven't tried yet as it is a little part of a big app
[21:06] <decke> but i've solved it by using static in the java classes (which was wrong in any case)
[21:07] <decke> i will write a little test app tomorrow to get an proper explanation what helma does...
[21:09] <decke> zumbrunn: could be interesting to test that too...
[21:13] * zumbrunn is noticing a solidifying pattern of drive-by commits by hannes
[21:14] <zumbrunn> great features always seem to get committed on Friday afternoons, before he disappears into the weekend
[21:16] <zumbrunn> (talking about the new sandbox feature in helma-ng)
[21:16] <zumbrunn> http://dev.helma.org/trac/helma/browser/helma-ng/trunk/modules/helma/system.js?rev=9571#L29
[21:17] <decke> i'm not yet familiar with ng...
[21:19] <decke> zumbrunn: is there already a timeline for 2.0 ?
[21:25] <zumbrunn> no, version 1.7 is next :-)

 

 

In the channel now:

Logs by date: