Sure, I'm looking for the rationale behind the two classes. That'll
help to determine how much of compatibility (if any) is broken because most of
them are similar. Also there are specific response types for the LoadBalancer
(ApplicationLoadBalancerResponse), GlobalLoadBalancerResponse which are
re
But, this will break backward compatibility no ?
Maybe change it in the next big release.
On 28/05/13 2:50 PM, "Prasanna Santhanam"
wrote:
>When I createFirewallRule I recieve a FirewallResponse but when I
>deleteFirewallRule I am expected to pass in an id I recieved as a
>FirewallRuleResponse?
When I createFirewallRule I recieve a FirewallResponse but when I
deleteFirewallRule I am expected to pass in an id I recieved as a
FirewallRuleResponse?
What are these two response types? They look very similar. Is this
legacy? Can we clean it up and standardize to a single
FirewallRuleResponse?
