Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Before it was acquired by Google, <a href="http://www.jot.com/" rel="nofollow noreferrer">JotSpot</a> used server-side JavaScript to let you query their database and display your pages. They used <a href="http://www.mozilla.org/rhino" rel="nofollow noreferrer">Rhino</a> to do it. CouchDB uses server-side JavaScript to create <a href="http://wiki.apache.org/couchdb/Views" rel="nofollow noreferrer">views</a> of their database.</p> <p>As you can see from these examples, a great way to use JavaScript on the server is for plugins. One of the reasons it's used is that you can create a very isolated sandbox for people to run their code in. Also, because of the way that JavaScript as a language works, you can provide a user tooling specifically honed to the tasks your users need to complete. If you do this right, users don't need to learn a new language to complete their tasks, a quick glance at your API and examples is enough to get them on their way. Compare this to many of the other languages and you can see why using server-side JavaScript to provide a plugin architecture is so enticing.</p> <p>A secondary popular solution, one which can be seen through a project like <a href="http://www.aptana.com/jaxer" rel="nofollow noreferrer">Jaxer</a>, is that a common problem of web applications that do client-side validation is that, since JavaScript is easily bypassed in the browser, validation has to be run once again on the server. A system like Jaxer allows you to write some validation functionality that is reusable between both server and client.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload