Mochabot log - CommonJS IRC channel: #commonjs on irc.freenode.net

2010-08-11:

[19:23] <nrstott> hey kriszyp , figured id jump in here if you need more info from me about that transporter problem
[19:24] <kriszyp> ok
[19:24] <kriszyp> do you have the console output of the error?
[19:24] <nrstott> the exception is simply not caught
[19:24] <nrstott> it seems to be uncachable for some reason
[19:24] <nrstott> it may be Yabbles fault...
[19:24] <kriszyp> who is throwing the error, the loader library?
[19:24] <kriszyp> oh, Yabble?
[19:24] <nrstott> yes
[19:25] <nrstott> it seemed as though the require exception were simply uncachable...
[19:26] <kriszyp> I'll try yabble...
[19:26] <nrstott> What do you usually use?
[19:26] <nrstott> requirejs?
[19:27] <kriszyp> well transporter has its own now (receiver.js), but I have been trying to test with requirejs, yabble, and receiver
[19:27] <kriszyp> and yabble works fine for me too with promise.js
[19:27] <nrstott> strange
[19:27] <nrstott> this may be related to other errors im having
[19:27] <kriszyp> not sure how it could throw an uncatchable error
[19:27] <nrstott> remember whe ni talked to you about the require("./base64") issue?
[19:28] <kriszyp> yeah
[19:28] <nrstott> well it turns out that only happens for locally referenced packages
[19:28] <nrstott> if i reference from github, it does not happen
[19:28] <nrstott> this may have the same behavior... id have to try it though
[19:29] <nrstott> i know that's not the best error report about the package issue... but hopefully itll give you some insight as to where the problem may be for "./" paths not finding their modules in referenced packages
[19:30] <kriszyp> any particular browser?
[19:32] <nrstott> firefox and chrome
[19:32] <nrstott> didnt try IE
[19:34] <nrstott> you want to see my package.json?
[19:34] <nrstott> i realy believe part of the problem may be that i am using local FS for promised-io
[19:34] <nrstott> "promised-io": "/home/nathan/working/promised-io/lib/",
[20:36] <nrstott> deanlandolt or kriszyp, what're the plans for supporting cookies in the JSGI Http Client in promised-io? I see a cookie jar with a TODO. I need this so I would like to take a stab at implementing.
[20:36] <deanlandolt> nrstott: please do :D
[20:38] <nrstott> deanlandolt, anything i should be aware of?
[20:38] <nrstott> is CookieJar just supposed to be a colletion of cookies to add to requests?
[20:39] <deanlandolt> it should be instance specific for starters, and the cookies should be stored and made available by domain, just as the browsers do...also like the browsers it should probably respect expiration times
[20:40] <nrstott> ok i wouldnt have expected it to be instance specific since there is simply an TODO exports.CookieJar
[20:40] <nrstott> but that would make sense
[20:40] <nrstott> so cookies should be a property of Client
[20:41] <deanlandolt> so really all you're doing is collecting set-cookie headers from the response and tucking them into memory based on the request's domain...then adding them to every request for that host
[20:41] <nrstott> right
[20:41] <deanlandolt> yeah, that's the idea of Client...though, perhaps it shouldn't necessarily be instance specific -- you should be able to provide the requisite cookie storage provider to the Client
[20:42] <nrstott> yeah so it should be a settable property
[20:42] <deanlandolt> that way you'd be able to share a cookie store between Client instances (just like you should be able to share a cache)
[20:42] <deanlandolt> yeah...should be something on this
[20:42] <deanlandolt> err `this`
[21:25] <nrstott> deanlandolt, I am taking an approach of making it middleware like your Redirect. I need a querystring utility. Should I jsut copy jacks? I know you guys probably dont want promised-io depending on jack
[21:25] <deanlandolt> sure i guess...but why a querystring utility?
[21:26] <nrstott> to parse the cookie strings
[21:26] <nrstott> they are really just querystrings
[21:26] <deanlandolt> well, sorta, yeah...but definitely don't borrow jack's :D
[21:26] <nrstott> why not?
[21:26] <nrstott> you know of a better one?
[21:28] <deanlandolt> no...but if you borrow jack's definitely take out the part where it does railsish stuff w/ foo[] => [foo] and foo[bar] => {foo: "bar"}

 

 

Logs by date :