AddResourceConfig: Difference between revisions
Jump to navigation
Jump to search
(Added description, fixed syntax, added argument descriptions, added return info, added categories) |
No edit summary |
||
| Line 24: | Line 24: | ||
==See Also== | ==See Also== | ||
{{Resource_functions}} | {{Resource_functions}} | ||
Revision as of 05:22, 1 January 2008
This function adds a new empty config file to an existing resource.
Syntax
xmlnode addResourceConfig ( resource theResource, string filename, [ string filetype = "server" ] )
Required Arguments
- theResource: the resource to which the config file will be added.
- filename: the name of the config file to be added.
Optional Arguments
NOTE: When using optional arguments, you might need to supply all arguments before the one you wish to use. For more information on optional arguments, see optional arguments.
- filetype: a string indicating whether the file is serverside ("server") or clientside ("client").
Returns
Returns the new config's root xmlnode if the config was added successfully, false otherwise.
Example
See Also
- abortRemoteRequest
- addResourceConfig
- addResourceMap
- call
- callRemote
- copyResource
- createResource
- deleteResource
- fetchRemote
- getRemoteRequestInfo
- getRemoteRequests
- getResourceACLRequests
- getResourceConfig
- getResourceDynamicElementRoot
- getResourceExportedFunctions
- getResourceFromName
- getResourceInfo
- getResourceLastStartTime
- getResourceLoadFailureReason
- getResourceLoadTime
- getResourceMapRootElement
- getResourceName
- getResourceOrganizationalPath
- getResourceRootElement
- getResources
- getResourceState
- getThisResource
- isResourceArchived
- isResourceProtected
- refreshResources
- removeResourceFile
- renameResource
- restartResource
- setResourceInfo
- startResource
- stopResource
- updateResourceACLRequest