Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write the shims.server #14

Open
aurium opened this issue Aug 13, 2014 · 2 comments
Open

Write the shims.server #14

aurium opened this issue Aug 13, 2014 · 2 comments
Assignees

Comments

@aurium
Copy link
Owner

aurium commented Aug 13, 2014

That must to work sooner as possible!

@ooflorent
Copy link
Contributor

I think we have a problem here.

All games should be able to run without the sandbox... The current design makes things really complicated. Last year, every server-side game had to serve its files using http and fs.

Here is a snippet from last year winning entry:

var fs = require('fs');
var app = require('http').createServer(handler),
    io = require('socket.io').listen(app);

function handler(req, res) {
  fs.readFile(/* ... */);
  /* ... */
}

So, should we serve game files or let games do it?
If we serve the files then the game will not be runnable in standalone...

@aurium
Copy link
Owner Author

aurium commented Aug 13, 2014

Well, we can consider this year the environment is not node itself, but this sandbox.

I believe the sandbox-io may be called by require('socket.io') inside the sandbox, also the same to the http and any shimed module... but that was not planned before. :-/

Can you implement it too on the sandboxer? So the sandbox and real node will not be so different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants