You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our implementation currently, only the Coordination AFFIX is responsible for the name. We provide the name/locator as one of the arguments for the Coordination AFFIX. This value does not get passed on to the other AFFIX components. Is this the correct way of doing it?
Furthermore, when we create an AFFIX stack through the AffixStackInterface, we provide an argument for the virtual_host_name which is used when the AFFIX stack is created. However this argument is not used for any other purpose other than AffixStack.gethostname() that returns this value.
The reason I originally did not pass the virtual_host_name to individual components is to ensure that the components did not change the name and return an ambiguous value when the method getmyip() is invoked.
Any thoughts on what should be done here? Should the virtual_host_name provided by the application be made available to all the AFFIX components or just to the AFFIX stack? If we do not make it available to every AFFIX component than a name will need to be passed down to decider and branching/splitter AFFIXs such as Coordination AFFIX and Legacy AFFIX.
The text was updated successfully, but these errors were encountered:
In our implementation currently, only the Coordination AFFIX is
responsible for the name. We provide the name/locator as one of the
arguments for the Coordination AFFIX. This value does not get passed on to
the other AFFIX components. Is this the correct way of doing it?
Furthermore, when we create an AFFIX stack through the
AffixStackInterface, we provide an argument for the virtual_host_name which
is used when the AFFIX stack is created. However this argument is not used
for any other purpose other than AffixStack.gethostname() that returns this
value.
The reason I originally did not pass the virtual_host_name to individual
components is to ensure that the components did not change the name and
return an ambiguous value when the method getmyip() is invoked.
Any thoughts on what should be done here? Should the virtual_host_name
provided by the application be made available to all the AFFIX components
or just to the AFFIX stack? If we do not make it available to every AFFIX
component than a name will need to be passed down to decider and
branching/splitter AFFIXs such as Coordination AFFIX and Legacy AFFIX.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23
.
In our implementation currently, only the Coordination AFFIX is responsible for the name. We provide the name/locator as one of the arguments for the Coordination AFFIX. This value does not get passed on to the other AFFIX components. Is this the correct way of doing it?
Furthermore, when we create an AFFIX stack through the AffixStackInterface, we provide an argument for the virtual_host_name which is used when the AFFIX stack is created. However this argument is not used for any other purpose other than AffixStack.gethostname() that returns this value.
The reason I originally did not pass the virtual_host_name to individual components is to ensure that the components did not change the name and return an ambiguous value when the method getmyip() is invoked.
Any thoughts on what should be done here? Should the virtual_host_name provided by the application be made available to all the AFFIX components or just to the AFFIX stack? If we do not make it available to every AFFIX component than a name will need to be passed down to decider and branching/splitter AFFIXs such as Coordination AFFIX and Legacy AFFIX.
The text was updated successfully, but these errors were encountered: