> you've only synchronous XHR to do that, You've made me think about this. I rejected sync XHR out-of-hand because the user interface would be blocked which of course is a horrible idea. But the Atom editor only hits the disk to load/save source files and sometimes to load/save options. And of course it hits it a lot when the app is loading. When editing a source file the disk it silent. So maybe sync XHR is worth considering.
> it's pretty restricted since all the new features of XHR aren't allowed in sync mode. What features would I be missing? I can't imagine anything other than making normal http requests. On Mon, Oct 27, 2014 at 10:15 PM, Mark Hahn <[email protected]> wrote: > > What're you dealing with that uses sync calls? > > OK, I wasn't going to admit how crazy I am, but I'm considering running > the Atom editor in the browser by providing all the node calls it needs. > What this really means is porting atom-shell to the browser. > > I'm not afraid of all the work involved, I just want to make sure it is > possible. Atom-shell and therefore Atom editor use almost all async fs > calls. This makes sense since it is a desktop app and two things aren't > running at once anyway. > > Browserify is already porting part of node to the browser. The missing > part is fs. I have used simulated file systems in the browser before with > emscripten and I'm pretty confident performance will be ok. I want to add > fs to browserify. > > > On Mon, Oct 27, 2014 at 8:59 PM, Aria Stewart <[email protected]> wrote: > >> >> > On 27 Oct 2014, at 23:54, Mark Hahn <[email protected]> wrote: >> > >> > > explicitly designed in the way so you cannot do this >> > >> > I understand. I am unfortunately facing a pragmatic problem that could >> be solved if a library could simulate a sync call with an async >> over-the-net call. >> > >> > Maybe I should restate the immense task I'd like to tackle. I'd like >> to implement node fs calls in the browser using the net to proxy to the >> server's file system. This includes sync fs calls. >> >> That's rough: you've only synchronous XHR to do that, and it's pretty >> restricted since all the new features of XHR aren't allowed in sync mode. >> >> What're you dealing with that uses sync calls? >> >> -- >> Job board: http://jobs.nodejs.org/ >> New group rules: >> https://gist.github.com/othiym23/9886289#file-moderation-policy-md >> Old group rules: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "nodejs" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/nodejs/oMNRWXwASOU/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/nodejs/676093CE-7DBC-4FE8-8F9C-25A0254E6C53%40nbtsc.org >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CACrj35Hze%2Br3%2Buv2_nanuFJ07SE-o7EhMhScjcXvBj2USOjVKQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
