2009-06-08:
[12:47] <hannesw> simono: interesting note you posted in #serverjs[12:47] <hannesw> i think it might be easy to add an optional second argument to org.mozilla.javascript.Synchronizer[12:47] <simono> oops yes, wanted to repost[12:48] <hannesw> well, it wasn't completely off topic over there :-)[12:50] <simono> what do you mean with sec arg? i could do a call() and pass in the "this" i want[12:50] <simono> i put pushychat up here http://github.com/smono/pushychat[12:50] <hannesw> no, an optional second argument to the Synchronizer constructor.[12:51] <hannesw> woohoo, github![12:51] <simono> :) oh you want to change rhino, that's out of scope for me :)[12:51] <hannesw> why? just file a bug, and eventually a committer will pick it up :-)[12:52] <hannesw> I think it makes sense to pass explicit sync objects[12:52] <simono> currently i'm fighting with org.mortbay.jetty.EofException .. something with one browser having two connections open and me doing smth stupid to the suspended request i think[12:52] <simono> okay i will file a bug[12:54] <hannesw> ok. i could do that too, if you prefer.[12:54] <hannesw> btw: Norman Rodderick?[12:55] <simono> arg... it's an old github account. alias for gaming[12:56] <simono> yes if you would.. that'd be great. same thing with the helmashell sync() function[12:57] <hannesw> i think we should put the sync() into helma/engine module? (currently helma/system)[12:57] <simono> yes[12:58] <simono> also i added servletRequest to req, was private before[13:02] <hannesw> yes, i added it too, forgot to commit it :-)[13:11] <simono> :)[13:14] <simono> ah git-diff is colored by default, i already like it[13:45] <simono> session won't get saved until the end of the request. so i can't store continuation for this session in there. any hints.. i'll check what ChatFilter does[15:24] <simono> hannesw, what do you mean by "outer page"?[15:24] <hannesw> simono: the html page[15:24] <simono> okay[15:25] <hannesw> if you make sure the session is initialized when you render the html page, you can assume it is there when you make the first XHR call[15:25] <simono> in real life probably not a problem, since users must be logged in[15:26] <simono> about request.session.c ... if a request stores a continuation there and then suspends it other requests following won't see session.c until the first request finished.[15:27] <hannesw> wait... maybe there's a problem with request.session.c vs. request.session.data.c[15:27] <hannesw> because it's supposed to be the latter...[15:27] <hannesw> I know, I don't like it either. it's too long.[15:28] <simono> okay.. i will carefully try that again.[15:31] <simono> hannesw, session.isNew needs a return statement and i added session.id[15:31] <hannesw> ok. thanks![15:35] <simono> must have messed up session.data access somewhere, works in test-app[15:39] <simono> damn did i private-reply you? i shouldn't use google-groups to write emails[15:49] <hannesw> :-)[21:01] <XaniTehRogue> Hey
In the channel now:
Logs by date: