Class List
Here are the classes, structs, unions and interfaces with brief descriptions:
- mi::nservices::Event_helper
- A helper class to facilitate event creation and sending
- mi::nservices::Event_helper_neuray
- A helper class to facilitate neuray event creation and sending
- mi::nservices::IAdmin_server_configuration
- Admin server configuration API component
- mi::nservices::IArgument_description
- Describes an argument to a service command
- mi::nservices::IBinary
- This interface represents binary data
- mi::nservices::ICanvas
- This interface represents a canvas
- mi::nservices::ICommand_context
- The context is which a command is executed
- mi::nservices::ICommand_context_neuray
- The context is which neuray commands are executed
- mi::nservices::ICommand_execute_response_handler
- Abstract interface called when command execution on a render loop has completed
- mi::nservices::ICommand_request
- A request to execute a web service command
- mi::nservices::ICommand_response
- A response from a neuray service command
- mi::nservices::IConverter
- Provides the ability to convert between different data types
- mi::nservices::IEvent
- Used to specify and send an event
- mi::nservices::IEvent_context
- The event context
- mi::nservices::IEvent_handler
- An Event handler. These are implemented by the user
- mi::nservices::IEvent_handler_context
- The event handler context. This is passed to event handlers when they are triggered,
- mi::nservices::IFactory
- Factory class for managing neuray services objects
- mi::nservices::IHttp_client
- HTTP Client Factory API Component for creating HTTP requests
- mi::nservices::IHttp_import_api
- Importer api interface over http and https protocols
- mi::nservices::IHttp_reader
- IReader implementation used for streaming the http response body
- mi::nservices::IHttp_request
- Represent an individual HTTP request
- mi::nservices::IHttp_response
- Represent an individual HTTP response as used in IHttp_response_handler
- mi::nservices::IHttp_response_handler
- User implemented response handler called with the response of the HTTP request
- mi::nservices::IPath_remapper
- This class is used to map relative paths passed in as arguments to commands to absolute paths on the local filesystem
- mi::nservices::IPick_response_handler
- Abstract interface called when a pick operation on a render loop has completed
- mi::nservices::IProgress_callback
- Abstract interface called when progress has been made during command execution
- mi::nservices::IRender_context
- The neuray services render context abstraction
- mi::nservices::IRender_loop
- Represents a render loop
- mi::nservices::IRender_loop_handler
- Defines a render loop handler
- mi::nservices::IRender_loop_handler_factory
- Factory class for creating render loop handlers
- mi::nservices::IRender_loop_handler_render_result
- A user implemented interface that returns the result of an individual render call in a render loop handler
- mi::nservices::IRender_loop_manager
- Management class for render loops
- mi::nservices::IRender_loop_render_counter_callback
- Abstract interface to report when the render loop has reached a specific counter
- mi::nservices::IRender_loop_rendered_callback
- Abstract interface called whenever a render loop renders a canvas
- mi::nservices::IScene
- The neuray services scene abstraction
- mi::nservices::IService_command
- Interface for Neuray Service Commands
- mi::nservices::ITonemap_context
- Defines a context in which a tonemapping operation is performed
- mi::nservices::ITonemap_operator
- Provides a contract for tone mapping implementations
- mi::nservices::IUser_type
- This interface represents user defined objects
- mi::nservices::IUser_type_definition
- A definition of a user type
- mi::nservices::Tonemap_operator< i_id1, i_id2, i_id3, i_id4, i_id5, i_id6, i_id7, i_id8, i_id9, i_id10, i_id11, I>
- This mixin class can be used to implement the minservices::ITonemap_operator interface