|Home > Iris APIs > Image loading and saving > Loading and saving an image|
Use the following functions to load and save images.
pathon the host that runs the target instance. If the file is only guaranteed to be accessible on the host that runs the client, clients should use
image_loadData()instead, and load the file in the client.
image_loadData()is semantically equivalent to
image_loadFile()except that this function does not open a file. Instead, it expects the image contents to be passed as an argument. Clients can use this function to push an image into an instance with a single function call. This function is intended for images that are small enough to be transferred as one uninterruptible chunk, typically up to a few megabytes. To load an image from the client side that is larger than that, use
image_loadData(), except that the image data is not provided as an argument but is pulled by the target instance from the client by calling the callback function
image_loadDataRead(). This interface enables:
image_load*()functions can optionally load arbitrary raw binary data, which is unformatted and without a header, into memory, by specifying the
image_load*()functions must return
E_function_not_supported_by_instancefor the functions that they do not support.
resource_read()inspect the state of the target instance. The client is responsible for formatting this data into the required image format and writing it to a file.
image_*()interface to write an image into a file that is accessible to the target instance. In other words, there is no
In a typical implementation:
executesSoftware=1property support the
memory_*()functions, not the