1. Types
2. content
3. library

## content library: optimization info

The `optimization_info` structure defines different optimizations and optimization parameters applied to particular library.

### Representations:

- JSON
- XML

{
"optimize_remote_publishing": true
}
<?xml version="1.0" ?>
<ns0:OptimizationInfo xmlns:ns0="http://vmware.com/content/library" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<optimize_remote_publishing>true</optimize_remote_publishing>
</ns0:OptimizationInfo>

#### Attributes:

Name | Type | Description
--- | --- | ---
Optional
optimize_remote_publishing | boolean | If set to `true` then library would be optimized for remote publishing. Turn it on if remote publishing is dominant use case for this library. Remote publishing means here that publisher and subscribers are not the part of the same `Vcenter` SSO domain. Any optimizations could be done as result of turning on this optimization during library creation. For example, library content could be stored in different format but optimizations are not limited to just storage format. Note, that value of this toggle could be set only during creation of the library and you would need to migrate your library in case you need to change this value (optimize the library for different use case). Optional. This field is optional for the `create` operation. If not specified for the `create`, the default is for the library to not be optmized for specific use case. It is not used for the `update` operation.