Re: Question on the sandbox
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 48214
interpreted = N
texte = Here is an excerpt from the tutorial on the ISP Sandbox feature that has been prepared by Scott Anderson. --------------------------------------------------------------------------Here is a list of WebDNA Tags and Contexts whose behavior is altered when used inside a WebDNA Sandbox... [appendfile] [writefile] [renamefile] [deletefile] [movefile] [copyfile] [fileinfo] [listfiles] [waitforfile] [copyfolder] [createfolder] [deletefolder] -------------- These contexts can only operate on files and or folders that exist within the Sandbox root folder, or the sandbox 'globals' folder when the '^' prefix is used. [orderfile] [purchase] [removelineitem] [clearlineitem] [setlineitems] [setheader] ------------- These operations can only operate on a cart or files that exists within the sandbox root, or the sandbox 'globals' folder when the '^' prefix is used. [flushdatabases] ---------------- Will only flush the databases that exists within the sandbox root or globals folder. [commitdatabase] [listdatabases] [closedatabase] [listfields] [search] [lookup] [replace] [append] [delete] --------------- These contexts will only operate on database files that exist within the sandbox root or globals folder. [protect ] ------------------ Uses the 'local' sandbox 'users.db' file [date] [time] ------ Both these tags use the 'format' preferences in the local sandbox prefs file [include] ------------------ Can only include a file that exists within the sandbox root or globals folder [sendmail] -------------- Uses the local sandbox email settings. Resulting email files are written to the sandbox 'EmailFolder'. [object] [dos] [applescript] ------------- These contexts require special handling, discussed later. [convertchars] ---------------- Uses the local sandbox 'StandardConversions.db' file. If a database is specified, it must exist within the sandbox root or globals folder. [convertwords] Can only be used with a database that exists within the sandbox root or globals folder.The '/' path prefix will be relative to the Sandbox root folder. The '^' global prefix will refer to the Sandbox globals folder and not the main WebDNA globals folder. The 'absolute path' specifier '*' can still be used with a sandbox, as long as it refers to a path that exists within the sandbox root or globals folder. WebDNA error messages will be retrieved from the sandbox ErrorMessages.db, and not the main WebDNA ErrorMessages.db WebDNA error logs and debug files will be created within the sandbox system folder, and not the main WebCatalogEngine folder. Shell, DOS, Applescript The [shell], [dos], and [applescript] contexts require special handling when used within a WebDNA Sandbox. Shell, DOS, and Applescript code can no longer be explicitly defined within these contexts, when used in a WebDNA Sandbox. Instead, the desired code must be submitted to the WebDNA admin for approval. If approved, the 'code snippet' is added to the WebDNA Sandbox 'Scripts' database, with a unique ID code. This ID code is then used by the Sandbox programmer. For example... A WebDNA sandbox programmer wants to execute the DOS command. dir c:\. The programmer submits the code snippet, dir c:\, to the WebDNA admin. The admin approves the code, and inserts the code into the WebDNA Sandbox Scripts database with a unique ID of '111'. The WebDNA admin then returns the ID to the Sandbox programmer. The Sandbox programmer then uses the ID as follows... [DOS scriptID=111][/DOS] The same applies when using the [shell] context. The [object] context is handled in a slightly different way. For this case, the submitted 'code snippet' is the 'parameter list' that would normally be passed into the context. For example.... [OBJECT objname=SystemInfo.SysInfo.1&type=0[!] [/!]&call=GetFreeDiskSpace[!] [/!]¶m1=C:\¶m1type=str][/OBJECT]would become...[OBJECT SCRIPTID=123][/OBJECT]The WebDNA admin having recorded the text: objname=SystemInfo.SysInfo.1&type=0[!] [/!]&call=GetFreeDiskSpace[!] [/!]¶m1=C:\¶m1type=strinto the Sandbox scripts database with an ID of 123.-----Original Message----- From: Rob Marquardt [mailto:rob@toastdesign.com] Sent: Friday, February 28, 2003 1:38 PM To: WebDNA Talk Subject: Question on the sandboxon 2/26/2003 1:45 pm, Phillip Bonesteele at pbonesteele@smithmicro.com so noted...> Any folder can be designated as a Sandbox, which then gets its own instance of > Prefs file, users.db, triggers.db, emailer preferences, global folder, email > folder, and admin templates. This essentially allows you to bind the entire > behavior of an instance of WebDNA to a particular folder, whereas in 4.X and > before the WebDNA behavior was bound to the entire server.What limitations does the sandbox place upon the use of things like [writefile], [deletefile], [applescript], [shell] and the Global Path prefix? Rob Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Here is an excerpt from the tutorial on the ISP Sandbox feature that has been prepared by Scott Anderson. --------------------------------------------------------------------------Here is a list of WebDNA Tags and Contexts whose behavior is altered when used inside a WebDNA Sandbox... [appendfile] [writefile] [renamefile] [deletefile] [movefile] [copyfile] [fileinfo] [listfiles] [waitforfile] [copyfolder] [createfolder] [deletefolder] -------------- These contexts can only operate on files and or folders that exist within the Sandbox root folder, or the sandbox 'globals' folder when the '^' prefix is used. [orderfile] [purchase] [removelineitem] [clearlineitem] [setlineitems] [setheader] ------------- These operations can only operate on a cart or files that exists within the sandbox root, or the sandbox 'globals' folder when the '^' prefix is used. [flushdatabases] ---------------- Will only flush the databases that exists within the sandbox root or globals folder. [commitdatabase] [listdatabases] [closedatabase] [listfields] [search] [lookup] [replace] [append] [delete] --------------- These contexts will only operate on database files that exist within the sandbox root or globals folder. [protect ] ------------------ Uses the 'local' sandbox 'users.db' file [date] [time] ------ Both these tags use the 'format' preferences in the local sandbox prefs file [include] ------------------ Can only include a file that exists within the sandbox root or globals folder [sendmail] -------------- Uses the local sandbox email settings. Resulting email files are written to the sandbox 'EmailFolder'. [object] [DOS] [applescript] ------------- These contexts require special handling, discussed later. [convertchars] ---------------- Uses the local sandbox 'StandardConversions.db' file. If a database is specified, it must exist within the sandbox root or globals folder. [convertwords] Can only be used with a database that exists within the sandbox root or globals folder.The '/' path prefix will be relative to the Sandbox root folder. The '^' global prefix will refer to the Sandbox globals folder and not the main WebDNA globals folder. The 'absolute path' specifier '*' can still be used with a sandbox, as long as it refers to a path that exists within the sandbox root or globals folder. WebDNA error messages will be retrieved from the sandbox ErrorMessages.db, and not the main WebDNA ErrorMessages.db WebDNA error logs and debug files will be created within the sandbox system folder, and not the main WebCatalogEngine folder. Shell, DOS, Applescript The [shell], [DOS], and [applescript] contexts require special handling when used within a WebDNA Sandbox. Shell, DOS, and Applescript code can no longer be explicitly defined within these contexts, when used in a WebDNA Sandbox. Instead, the desired code must be submitted to the WebDNA admin for approval. If approved, the 'code snippet' is added to the WebDNA Sandbox 'Scripts' database, with a unique ID code. This ID code is then used by the Sandbox programmer. For example... A WebDNA sandbox programmer wants to execute the DOS command. dir c:\. The programmer submits the code snippet, dir c:\, to the WebDNA admin. The admin approves the code, and inserts the code into the WebDNA Sandbox Scripts database with a unique ID of '111'. The WebDNA admin then returns the ID to the Sandbox programmer. The Sandbox programmer then uses the ID as follows... [DOS scriptID=111][/DOS] The same applies when using the [shell] context. The [object] context is handled in a slightly different way. For this case, the submitted 'code snippet' is the 'parameter list' that would normally be passed into the context. For example.... [OBJECT objname=SystemInfo.SysInfo.1&type=0[!] [/!]&call=GetFreeDiskSpace[!] [/!]¶m1=C:\¶m1type=str][/OBJECT]would become...[OBJECT SCRIPTID=123][/OBJECT]The WebDNA admin having recorded the text: objname=SystemInfo.SysInfo.1&type=0[!] [/!]&call=GetFreeDiskSpace[!] [/!]¶m1=C:\¶m1type=strinto the Sandbox scripts database with an ID of 123.-----Original Message----- From: Rob Marquardt [mailto:rob@toastdesign.com] Sent: Friday, February 28, 2003 1:38 PM To: WebDNA Talk Subject: Question on the sandboxon 2/26/2003 1:45 pm, Phillip Bonesteele at pbonesteele@smithmicro.com so noted...> Any folder can be designated as a Sandbox, which then gets its own instance of > Prefs file, users.db, triggers.db, emailer preferences, global folder, email > folder, and admin templates. This essentially allows you to bind the entire > behavior of an instance of WebDNA to a particular folder, whereas in 4.X and > before the WebDNA behavior was bound to the entire server.What limitations does the sandbox place upon the use of things like [writefile], [deletefile], [applescript], [shell] and the Global Path prefix? Rob Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Phillip Bonesteele
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Authorize.net setup (2002)
Almost a there but..bye bye NetCloak (1997)
3 card formulas! (1999)
HTML encoding in URLs (1997)
local IIS setup (2004)
WebCat2: Found Items syntax, etc. (1997)
Editing the search string (1997)
Sku numbers (1997)
Guestbook (2000)
WebCatalog can't find database (1997)
when is date system date or order date? (1997)
Emailer choke (1997)
Exclude by date - multiple (1997)
Lost and Recovered. (1998)
Extended [ConvertChars] (1997)
Queertrons? (1997)
[WebDNA] remove html comments (2009)
Clear command and ShoppingCart.tmpl (1997)
Reversed words (1997)
[WebDNA] Bug in [thisurlplusget] on v7 (2011)