Use-cases for v8cgi

[Christoph Dorn]

I will be presenting a 30 minute keynote talk at Wakanday [1] (Oct 15)
and wish to mention v8cgi specifically.

To highlight v8cgi in the best possible way I am looking for a list of
use-cases for the platform.

I would greatly appreciate a **comprehensive braindump** of the
various places v8cgi is going to go in the short and long term and
what is generally possible. The idea is to inspire a new audience and
paint a picture of why someone would choose and invest in v8cgi.

I would imagine this list would include (please include status of use-
case/features):

* Command-line scripts (implemented)
* Apache module (implemented)
* Server side image rendering via GD (implemented)
* Full DOM support to render DOM-based templates server-side
(implemented)
* MySQL bindings to write DB web services (implemented)
* SSL support for secure communication at all levels (planned)
* Hassle-free deployment of JS server apps by attaching a zip
archive to a virtual host (possible)

If you have links to various different examples/integrations/
discussions I would be happy to include them but that is not
necessary.

If you are interested in helping me promote CommonJS by mentioning
v8cgi, an implementation that seeks to be CommonJS compliant, please
respond ASAP. Sorry about the short notice!

Thanks!
Christoph

[1] - http://wakanday.org/

[Ondřej Žára]

Hi Christoph,

thanks a lot for paying so much attention to v8cgi. Here is the list of suggested features/use-cases for v8cgi, as I currently see it:

- command-line shell scripting in JS (implemented)
- relatively simple way to experiment with SSJS on all major platforms (windows builds provided)
- simple interfacing with existing HTTP solutions via CGI, FastCGI, Apache module (implemented)
- support for php-like web page development (implemented)
- a decent set of built-in libraries, both JS and native: (for a full list, see http://code.google.com/p/v8cgi/wiki/API)
  - sockets (create own server; connect to remote services)
  - databases (connect to sqlite, mysql, pgsql)
  - gd (read, write, manipulate images)
  - zlib (compress and decompress data)
  - dom (to re-use client-side code on server)
  - memcached
  - ssl (planned; to allow secure socket communication)
- synchronous interface (as opposed to node.js) for more straight-forward usage; suitable for users coming from php etc
- commonjs compliance as a top priority (in contrast with node.js, but I may be wrong): possible reuse of all (non-native) SSJS modules written for commonjs-compatible platforms

It might also be worth mentioning that several things are missing and/or incomplete:

- logo, PR
- debian/ubuntu packaging (current priority #1, unfortunately I have zero experience with this)
- more testing, more unit tests, code reviews
- package manager (npm)


Hope the list is sufficient,
Ondrej Zara

2011/10/4 Christoph Dorn <chri...@christophdorn.com>

--
You received this message because you are subscribed to the Google Groups "v8cgi" group.
To post to this group, send email to v8...@googlegroups.com.
To unsubscribe from this group, send email to v8cgi+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/v8cgi?hl=en.