- From: <piranna@gmail.com>
- Date: Sun, 20 Oct 2013 19:46:56 +0200
- To: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
- Message-ID: <CAKfGGh2nHbx37TBMtthQJZZPfaH0rbhVjG+t_78tkfwBJ4RWag@mail.gmail.com>
> > > Look at IndexedDB API, since asynchronous one was enought dfor everybody, > synchronous one was not implemented by the browsers and now it has became > deprecated... :-) > > Well regarding my position I would not smile ;-) > I was considering a server-side implementation of indexedDB. There is > currently the indexeddb-js project for Node using sqlite-3 > I have in my background todo list to develop one of them ;-) This case, using LevelDB as base database instead of SQLite (I'm a fan of it, but this is not the correct use case for it). and should be considered by clients as remote workers (the server let debug > those contexts via Web Inspector). > > Interesting concept, seems we both see WebSockets and WebWorkers are cousins (the only diference in the API is just one use send() and the other postMessage() ). Have you tried to propose this RemoteWorkers as a standard? > I like the JavaScript EventLoop strength for async coding, as I > appreciates the upcoming promises, but still, as some people in this list I > think that synchronous code is more user friendly. > For general purposes and as a general statement, yes, it's more user friendly, but for some use cases asynchronous code is more eficient and up to some point more user friendly once you understand it correctly. -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Sunday, 20 October 2013 17:47:43 UTC