Per the preceding discussion in #53, and sitting on top of #54, poll the instances for a VIP address periodically. This implements the "consuming" capability mentioned in #53, with a contraction in the method names down to EurekaConnection.ScheduleVIPAddressUpdates and EurekaConnection.ScheduleSecureVIPAddressUpdates, not mentioning the word "instance" there.
I used the same "functional options" technique first appearing in #54 for the following options that one can supply to GetInstancesByVIPAddress, GetInstancesBySecureVIPAddress, ScheduleVIPAddressUpdates, and ScheduleSecureVIPAddressUpdates:
WithStatus
ThatAreUp
Shuffled
ShuffledWith
I intend to apply those options to the "caching" factory functions as well.
Per the preceding discussion in #53, and sitting on top of #54, poll the instances for a VIP address periodically. This implements the "consuming" capability mentioned in #53, with a contraction in the method names down to
EurekaConnection.ScheduleVIPAddressUpdates
andEurekaConnection.ScheduleSecureVIPAddressUpdates
, not mentioning the word "instance" there.I used the same "functional options" technique first appearing in #54 for the following options that one can supply to
GetInstancesByVIPAddress
,GetInstancesBySecureVIPAddress
,ScheduleVIPAddressUpdates
, andScheduleSecureVIPAddressUpdates
:WithStatus
ThatAreUp
Shuffled
ShuffledWith
I intend to apply those options to the "caching" factory functions as well.