Not Supported
The following features are not currently supported in SpeedLink:
| • | Automatic rescheduling of failed Service operations—any failed operation is immediately reported to the application as an invocation failure exception. This is primarily because there is no optimization advantage to having the SpeedLink code retry versus customer code. |
| • | Redundant scheduling, since it has no benefit in low latency applications. |
| • | Data encryption, data compression, or SSL. |
| • | State update. |
| • | Invocation cancellation. |
| • | Task resubmission. |
| • | Operation-level discrimination. |
| • | Deferred collection such as COLLECT_LATER and COLLECT_NEVER. |
| • | Proxies are not supported; client code must use the Service.submit or execute methods to invoke Service code. |
| • | SpeedLink does not support the XML Serialization mode, which is typically only used when you require cross-language use of objects, or when a client does not have access to the Service implementation classes. |