1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263
|
/* $Header$ */
/*
* Copyright (c) 1999, 2002 Michael J. Roberts. All Rights Reserved.
*
* Please see the accompanying license file, LICENSE.TXT, for information
* on using and copying this software.
*/
/*
Name
vmhost.h - T3 VM host interface
Function
The host interface defines a set of services that the VM obtains from
its host application environment. The VM uses the host interface to
obtain these services so that the VM doesn't have to make too many
assumptions about the larger application of which it is a subsystem.
Every application containing the VM must provide the VM with an
implementation of this interface.
Notes
Modified
07/29/99 MJRoberts - Creation
*/
#ifndef VMHOST_H
#define VMHOST_H
#include "os.h"
/* ------------------------------------------------------------------------ */
/*
* I/O Safety Levels. These are defined as integers, not an enum, because
* they form a hierarchy; a higher value imposes all of the restrictions of
* all lower values, plus additional restrictions of its own.
*
* In the past, there was a single safety level that controlled both read
* and write. In 3.1 we separated the read and write levels. Because
* of the history, each level specifies separate read and write permissions
* that were formerly combined in that level. The descriptions still apply
* even though we track the levels separately - some levels must be
* interpreted differently for reading vs writing. For example, if the
* read level is 3, it allows current-directory reading, but if the write
* level is 3, it denies all write access. Separating the levels allows
* for combinations that weren't formerly possible: for exmaple, -s04 (read
* 0, write 4) allows reading anywhere but writing nowhere.
*/
/* level 0: minimum safety; read/write any file */
const int VM_IO_SAFETY_MINIMUM = 0;
/* level 1: read any file, write only to files in the current directory */
const int VM_IO_SAFETY_READ_ANY_WRITE_CUR = 1;
/* level 2: read/write in current directory only */
const int VM_IO_SAFETY_READWRITE_CUR = 2;
/* level 3: read from current directory only, no writing allowed */
const int VM_IO_SAFETY_READ_CUR = 3;
/* level 4: maximum safety; no file reading or writing allowed */
const int VM_IO_SAFETY_MAXIMUM = 4;
/* ------------------------------------------------------------------------ */
/*
* Network safety levels.
*/
/* level 0: minimum safety; all network access */
const int VM_NET_SAFETY_MINIMUM = 0;
/* level 1: localhost access only */
const int VM_NET_SAFETY_LOCALHOST = 1;
/* level 2: no network access */
const int VM_NET_SAFETY_MAXIMUM = 2;
/* ------------------------------------------------------------------------ */
/*
* get_image_name return codes
*/
enum vmhost_gin_t
{
/*
* get_image_name() call ignored - this is returned if the host
* system doesn't have a way of asking the user for an image name,
* so the caller must rely on whatever other way it has of finding
* the image name (which usually means that it can't find a image
* name at all, given that it would only call get_image_name() when
* it can't otherwise find the name)
*/
VMHOST_GIN_IGNORED,
/*
* user chose not to supply an image name - this is returned when,
* for example, the user cancelled out of a file selector dialog
*/
VMHOST_GIN_CANCEL,
/*
* error - the host system can't prompt for a filename because of
* some kind of error (not enough memory to load a dialog, for
* example)
*/
VMHOST_GIN_ERROR,
/* success */
VMHOST_GIN_SUCCESS
};
/* ------------------------------------------------------------------------ */
/*
* T3 VM Host Application Interface. This is an abstract class; it must
* be implemented by each application that embeds the VM.
*/
class CVmHostIfc
{
public:
virtual ~CVmHostIfc() { }
/*
* Get the file I/O safety read and write levels. These allow the host
* application to control the file operations that a program running
* under the VM may perform. See the VM_IO_SAFETY_xxx values above.
*/
virtual int get_io_safety_read() = 0;
virtual int get_io_safety_write() = 0;
/*
* set the I/O safety level - this should only be done in response
* to a user preference setting (such as via a command-line option),
* never as a result of some programmatic operation by the executing
* image
*/
virtual void set_io_safety(int read_level, int write_level) = 0;
/*
* Get the network safety level settings. This works like the I/O
* safety level, but applies to network access. The client level
* controls the game's access to network services as a client, such as
* the game making http requests of a web server. The server level
* controls the game's ability to create network services that accept
* incoming connections from other processes and machines.
*/
virtual void get_net_safety(int *client_level, int *server_level) = 0;
/*
* Set the network safety level.
*/
virtual void set_net_safety(int client_level, int server_level) = 0;
/*
* Get the resource loader for system resources (character mapping
* tables, the timezone database, etc). This resource loader should be
* set up to load resources out of the VM executable or out of the
* directory containing the VM executable, since these resources are
* associated with the VM itself, not the T3 program executing under
* the VM.
*/
virtual class CResLoader *get_sys_res_loader() = 0;
/*
* Set the image file name. The VM calls this after it learns the
* name of the image file so that the host system can access the
* file if necessary.
*/
virtual void set_image_name(const char *fname) = 0;
/*
* Set the root directory path for individual resources (such as
* individual image and sound resources) that we don't find in the
* image file or any attached resource collection file. If this is
* never called, the directory containing the image file should be used
* as the resource root directory.
*/
virtual void set_res_dir(const char *fname) = 0;
/*
* Add a resource collection file. The return value is a non-zero file
* number assigned by the host system; the VM uses this number in
* subsequent calls to add_resource() to add resources from this file.
* The VM cannot add any resources for a file until it first adds the
* file with this routine.
*/
virtual int add_resfile(const char *fname) = 0;
/*
* Determine if additional resource files are supported - if this
* returns true, add_resfile() can be used, otherwise add_resfile()
* will have no effect.
*/
virtual int can_add_resfiles() = 0;
/*
* Add a resource map entry. 'ofs' is the byte offset of the start
* of the resource within the file, and 'siz' is the size in bytes
* of the resource data. The resource is stored as contiguous bytes
* starting at the given file offset and running for the given size.
* The 'fileno' is zero for the image file, or the number assigned
* by the host system in add_resfile() for other resource files.
*/
virtual void add_resource(unsigned long ofs, unsigned long siz,
const char *res_name, size_t res_name_len,
int fileno) = 0;
/*
* Add a resource link map entry. This creates an association between
* a compiled resource name and a filename in the local file system.
* This is used primarily for debugging purposes, so that the compiler
* can avoid copying the resource data, instead simply placing a link
* for each resource to its local file copy.
*/
virtual void add_resource(const char *fname, size_t fnamelen,
const char *res_name, size_t res_name_len) = 0;
/*
* Find a resource. Returns an osfildef* handle to the open resource
* file if the resource can be found; the file on return will have its
* seek position set to the first byte of the resource in the file,
* and *res_size will be set to the size in bytes of the resource
* data. If there is no such resource, returns null.
*/
virtual osfildef *find_resource(const char *resname, size_t resname_len,
unsigned long *res_size) = 0;
/*
* Get the external resource file path. If we should look for
* resource files in a different location than the image file, the
* host system can set this to a path that we should use to look for
* resource files. If this is null, the VM should simply look in
* the same directory that contains the image file. If the host
* system provides a path via this routine, the path string must
* have a trailing separator character if required, so that we can
* directly append a name to this path to form a valid
* fully-qualified filename.
*/
virtual const char *get_res_path() = 0;
/*
* Determine if a resource exists. Returns true if so, false if
* not.
*/
virtual int resfile_exists(const char *res_name, size_t res_name_len) = 0;
/*
* Ask the user to supply an image file name. We'll call this
* routine only if we can't obtain an image file from command line
* arguments or from an attachment to the executable.
*/
virtual vmhost_gin_t get_image_name(char *buf, size_t buflen) = 0;
/*
* Get a special system filename path. This is essentially a wrapper
* for os_get_special_path() that encapsulates the information needed
* for that function. The 'id' value has the same meaning as in
* os_get_special_path() (see tads2/osifc.h).
*/
virtual void get_special_file_path(char *buf, size_t buflen, int id) = 0;
};
#endif /* VMHOST_H */
|