Oops, I think I just broke it. I scrolled right down the list of past chains (utterly ingenious, by the way) before finishing my newest task and submitting it, and now I get an internal server error.
Doodle or Die - our "bizarrely addictive" Node Knockout game
51–60 of 71 posts
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#52You can greatly decrease your load by making each thread link-able and then linking to each, not displaying _all_ of them each time.
Thanks for the suggestion. We plan on doing that after the competition. It's crazy that it works at all the way it is now. What you see was built in about 8 hours, at a bar, using an iPhone for internet.
If you can manage to keep the last few displaying, and not link all of them, it would make for an easier time viewing your recent drawings. This game is a blast seeing how these threads develop.
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#53Oops, I think I just broke it. I scrolled right down the list of past chains (utterly ingenious, by the way) before finishing my newest task and submitting it, and now I get an internal server error.
I get one too t.t
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#54I'm happy to answer any questions about the game or using Node.
Where did you host your mongodb instance at? How has your experience been with no.de?
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#55Earlier quoted context omitted.
Or it was coded in 8 hours. . .
But isn't this one of the selling points of node.js? From their site: "Node's goal is to provide an easy way to build scalable network programs. In the "hello world" web server example above, many client connections can be handled concurrently." I've noticed a few sites hosted at no.de go down after hitting the HN front page. I'd like to know the answers to the questions posed by the grandparent.
Part of the issue might be that Joyent's virtual Node servers, at least the ones used by Node Knockout competitors, have 120 megs RAM.
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#56I'm kind of impressed with how quickly I encountered dicks. I guess this is chat roulette 2.0. Really fun and impressive work otherwise though.
An easy way to make the thread interesting again is to describe them as rocket ships, or pickles, or...well you get the picture.
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#57Oops, I think I just broke it. I scrolled right down the list of past chains (utterly ingenious, by the way) before finishing my newest task and submitting it, and now I get an internal server error.
same here. I did the same thing, but I think it's probably just that the server crashed, while I was drawing. I'm trying to resubmit every few minutes. Hopefully my epicness won't be lost
edit: oh wait, it's back up
edit2: damn, down again. Express error: http://cl.ly/2d122W2x3l0y253o0y3O
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#58Now getting a 500:
Express 500 Error: notConnected
at [object Object].executeCommand (/home/node/local/lib/node_modules/mongodb/lib/mongodb/db.js:708:41)
at Collection.findOne (/home/node/local/lib/node_modules/mongodb/lib/mongodb/collection.js:753:11)
at /home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:143:16
at MongoStore._get_collection (/home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:92:19)
at MongoStore.get (/home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:142:8)
at Object.session [as handle] (/home/node/local/lib/node_modules/express/node_modules/connect/lib/middleware/session.js:319:11)
at next (/home/node/local/lib/node_modules/express/node_modules/connect/lib/http.js:198:15)
at IncomingMessage. (/home/node/local/lib/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:74:9)
at IncomingMessage.emit (events.js:61:17)
at HTTPParser.onMessageComplete (http.js:133:23)Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#59at [object Object].executeCommand (/home/node/local/lib/node_modules/mongodb/lib/mongodb/db.js:708:41)
at Collection.findOne (/home/node/local/lib/node_modules/mongodb/lib/mongodb/collection.js:753:11)
at /home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:143:16
at MongoStore._get_collection (/home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:92:19)
at MongoStore.get (/home/node/local/lib/node_modules/connect-mongo/lib/connect-mongo.js:142:8)
at Object.session [as handle] (/home/node/local/lib/node_modules/express/node_modules/connect/lib/middleware/session.js:319:11)
at next (/home/node/local/lib/node_modules/express/node_modules/connect/lib/http.js:198:15)
at IncomingMessage. (/home/node/local/lib/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:74:9)
at IncomingMessage.emit (events.js:61:17)
at HTTPParser.onMessageComplete (http.js:133:23)
Re: Doodle or Die - our "bizarrely addictive" Node Knockout game
#60Earlier quoted context omitted.
But isn't this one of the selling points of node.js? From their site: "Node's goal is to provide an easy way to build scalable network programs. In the "hello world" web server example above, many client connections can be handled concurrently." I've noticed a few sites hosted at no.de go down after hitting the HN front page. I'd like to know the answers to the questions posed by the grandparent.
Part of the issue might be that Joyent's virtual Node servers, at least the ones used by Node Knockout competitors, have 120 megs RAM.
That makes sense. I didn't know that. Thanks.