Client and Server JavaScript APIs Community Group Proposed

The Client and Server JavaScript APIs Community Group has been proposed:

--------------------------------------------------

REST seven's rule was "Code on Demand", meaning the ability for the
server to deliver code able to run on the client. Some, to use the same
code everywhere, tried to do it with Java, .NET (ActiveX). Today, even
Flash is fading out to let this place to JavaScript.
HTML5 and offline support contributed in the creation of a bunch of APIs
which only made sense on server-side in first place: File/FileSystem,
Workers, Sockets, Storage/Session, Blob, ImageData. Most of those APIs,
and even the already existing XMLHttpRequest (now in version 2) have
been designed from the beginning to be usable via either synchronous or
asynchronous APIs from the very early stages (synchronous is not
blocking any more the user interface in browsers when used in workers).




Now that the Server-Side JavaScript is rising again either in
synchronous and asynchronous implementations, it is time, if we really
want interoperable code/libraries/modules, to make those APIs taking
into account the server-side context, and then on the other end, to push
Server-Side JavaScript implementations to support them. CommonJS started
a great project, it is now time to make its ambitions real.

--------------------------------------------------

You are invited to support the creation of this group:
  http://www.w3.org/community/groups/proposed#jseverywhere

Once the group has a total of five supporters, W3C launch the group
and people can join to begin work.

In order to join the group, you will need a W3C account. To request one:
  http://www.w3.org/community/account/request

If you believe that there is an issue with this group that requires
the attention of the W3C staff, please send us email on
site-comments@w3.org.

Thank you,
W3C Community Development Team

Received on Wednesday, 18 April 2012 13:24:31 UTC