You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to js.io
There has been some discussion whether or not js.io should expose data
storage - and if so, which type of data storage.
The agreement seems to be that, yes, js.io should expose a data
storage, because precious few interesting applications can be
developed without storage.
So what type of storage? Relational? Key Value pair? Document based?
I think CouchDB seems really awesome - scales horizontally, uses map
reduce to grab/process data (which javascript lends itself to
beautifully) and has a browser implementation of the API for the local
testing environment.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to js.io
Hi,
I'm in the process of releasing a server that exposes a few different
data storage APIs to the browser. It has an AJAX API that's
automatically wrapped in Javascript
The thing about exposing data storage is that there's no good 1-size-
fits-all approach. Sometimes you can get away with merely serializing
to JSON and shoving everything into a text file, and other times you
need something more complicated. I have "document," name-value pairs,
relational, and I also have a system to allow for server-side
javascript when it becomes impossible to have proper security without
some kind of server-side logic.
I will have a release sometime this week once a few licensing issues
get worked out.