It's an unfortunate name, but I cannot come up with anything better that
is not absurdly long.
For the record, the generic name "NetworkInterfaceSpec" sounds like a
problem because this is actually a set of options that only really make
sense in the specific context of RunInstances. We already have another
bag of data that only really makes sense in the context of
CreateNetworkInterface. If we need one more, will we name it
NetworkInterface..Data?..Stuff?
https:/ /codereview. appspot. com/60620043/ diff/60001/ ec2/ec2. go
File ec2/ec2.go (right):
https:/ /codereview. appspot. com/60620043/ diff/60001/ ec2/ec2. go#newcode204 eSpec encapsulates options for a
ec2/ec2.go:204: // NetworkInterfac
single network
Ah, and as we discussed, this type should be something along the lines
of
RunNetwork Interface
It's an unfortunate name, but I cannot come up with anything better that
is not absurdly long.
For the record, the generic name "NetworkInterfa ceSpec" sounds like a terface. If we need one more, will we name it e..Data? ..Stuff?
problem because this is actually a set of options that only really make
sense in the specific context of RunInstances. We already have another
bag of data that only really makes sense in the context of
CreateNetworkIn
NetworkInterfac
https:/ /codereview. appspot. com/60620043/