Issue migrated from google code
After CloudObject's constructor invocation, some scenarios involve some amount of interaction/additional configuration before starting expensive operation on cloudObject. However, within the current design of the CloudScale, this initial configuration will happen through remote invocation that can significantly impact performance.
If we introduce additional annotation that will allow to deploy/migrate completely-configured object to the cloud before (after) some method invocation, we may cover more use cases and give more flexibility to the users.
If the annotation is not present or constructor is annotated, the behavior remains the same.
Issue migrated from google code
After CloudObject's constructor invocation, some scenarios involve some amount of interaction/additional configuration before starting expensive operation on cloudObject. However, within the current design of the CloudScale, this initial configuration will happen through remote invocation that can significantly impact performance.
If we introduce additional annotation that will allow to deploy/migrate completely-configured object to the cloud before (after) some method invocation, we may cover more use cases and give more flexibility to the users.
If the annotation is not present or constructor is annotated, the behavior remains the same.