Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
custom:javascript [2019/05/06 02:05] – [See Also] digital mancustom:javascript [2019/05/27 21:35] – [Integration] renamed to Invocation and provided more details. digital man
Line 39: Line 39:
 Modified stock ''.js'' files should be placed in your Synchronet ''[[dir:mods]]'' directory to prevent over-writing by future upgrades.  Modified stock ''.js'' files should be placed in your Synchronet ''[[dir:mods]]'' directory to prevent over-writing by future upgrades. 
  
-===== Integration =====+===== Invocation =====
  
-JavaScript files can be executed from:+JavaScript files can be executed / invoked from:
   * [[:server:terminal|Terminal Server]]   * [[:server:terminal|Terminal Server]]
-as a timed event, external program (door), login/logon/newuser module, +as a timed event, external program (door), login/logon/newuser module, via the ''EXEC'' sysop command 
-basically anywhere a Baja module or executable can be launched+((basically anywhere a Baja module or native or MS-DOS executable can be launched))
   * [[:server:web|Web Server]]   * [[:server:web|Web Server]]
-dynamically generates HTML files,+dynamically generates HTTP responses (e.g. HTML/CSS content),
 see ''[[dir:web]]/root/*.ssjs'' see ''[[dir:web]]/root/*.ssjs''
   * [[:server:ftp|FTP Server]]   * [[:server:ftp|FTP Server]]
Line 57: Line 57:
 inbound mail processors may be written in JavaScript,  inbound mail processors may be written in JavaScript, 
 see ''[[dir:exec]]/[[module:mailproc_example]].js'' and ''[[dir:ctrl]]/[[config:mailproc.ini]]'' see ''[[dir:exec]]/[[module:mailproc_example]].js'' and ''[[dir:ctrl]]/[[config:mailproc.ini]]''
-  * [[:util:jsexec|JSexec]] +  * [[:util:JSexec]] 
-some script files may be executed outside of Synchronet (e.g. as a CGI script or daemon) using jsexec,+some script files may be executed outside of Synchronet (e.g. as a CGI script or daemon) using [[util:JSexec]],
 examples: ''ircd.js'', ''newslink.js'' examples: ''ircd.js'', ''newslink.js''
  
-From the Terminal Server, a JavaScript file is executed on a native command-line by placing a question mark (''?'') at the beginning of the command-line before the JavaScript file name (in [[util:scfg]]). It is not necessary to specify the ''.js'' portion of the file name on the command-line. For example, the command-line to execute the file ''[[dir:exec]]/newslink.js'' would be "''?newslink''" or "''?newslink.js''".+From the Terminal Server, a JavaScript file is executed on a native command-line by placing a question mark (''?'') or asterisk (''*'') at the beginning of the command-line before the JavaScript file name (in [[util:SCFG]]). It is not necessary to specify the ''.js'' portion of the file name on the command-line. For example, the command-line to execute the file ''[[dir:exec]]/newslink.js'' would be "''?newslink''" or "''*newslink''".
  
 From within a Baja module, a JavaScript file may be executed using the following Baja code: From within a Baja module, a JavaScript file may be executed using the following Baja code:
Line 67: Line 67:
 exec "?modname" # where modname is the JavaScript file. exec "?modname" # where modname is the JavaScript file.
 </code> </code>
 +or: 
 +<code baja> 
 +exec "*modname" # where modname is the JavaScript file. 
 +</code>
 ===== Object Model ===== ===== Object Model =====
  

Trace: