[7:51]<zumbrunn> simono: req.GET isn't really that ideal either [7:51]<zumbrunn> I don't think I would prefer it over req.queryParams [7:52]<zumbrunn> I *would* prefer req.get [7:52]<zumbrunn> but that's already in use [8:07]<simono> hm, maybe req.query and req.post ... what don't you like about req.GET? the all-uppercase? [8:09]<zumbrunn> yes, the all uppercase seems out of place [8:15]<simono> well it looks like a constant array and thats what it should be and in html-form it should be written all uppercase as well.. so i find it consistent [8:16]<simono> i'm just very unhappy about queryParams being so long and not really in-sync with how it's called everywhere else [8:17]<zumbrunn> everywhere else being where for example? [8:17]<zumbrunn> (other than in the html-form) [8:22]<zumbrunn> you could set global.GET = req.queryParams; in an onRequest handler [8:47]<simono> well that would be everywhere else.. html-forms and http-headers. i'll try the global.GET and see how that looks [8:49]<zumbrunn> ok, I thought you meant other frameworks/environments [8:59]<simono> well that too.. php, python .. and django, and those django ppl are really anal about not confusing post/get