Deploying JNEXT

[Pinal]

This may be a very dumb question, but I have to ask. What needs to be
deployed in order to use the JNEXT framework? Is it just install JNEXT
on the web server and configure the auth.txt to allow specific domains
to access specific plugins? Is there any deployment involved on the
client-side (browser machines). The reason I ask this is because the
JNEXT socket sample work fine locally on my box where JNEXT framework
is installed, but does work on another machine; I get a javascript
error saying "Object doesn't support this property or method".

[Pinal]

Got more info; on the remote machine it's failing in the init()
function of sockets.js at "if ( !
g_JNEXTDispatcher.require( "Sockets" ) )".

[Amnon David]

JNEXT has to be installed on every machine where you'd want access to
native resources (such as sockets) from within a page in the Web
browser. In this aspect, it is a client side framework much like Adobe's
AIR or Microsoft's SilverLight (only smaller in terms of footprint and
learning curve...)

Whether you're writing a local application as a set of HTML files that
will be installed on the end user's box or creating a Web site with
special functionality, users will need to install the JNEXT on their
system before installing your HTML application or browsing your Web
site. Among the planned features in the next version is an easier way
for the end user to decide whether to authorize a site's to access JNEXT
components.

By the way, I assume that in your case the line:

g_JNEXTDispatcher.require( "Sockets" )

fails because the JNEXT Sockets.dll plugin is not available (probably
because JNEXT is not installed on the system).

-Amnon