We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With the introduction of ArtD we have situations where we want to describe a group of servers/services. This lacks in the documentation today
With the new event this scenario can appear and we should document how we think Eiffel can describe this.
A best-practice/description on how Eiffel can describe a group of servers/services
Having documentation of how we describe a group of servers/services user of Eiffel have a best-practice how to make this description.
None that I can think of
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
With the introduction of ArtD we have situations where we want to describe a group of servers/services. This lacks in the documentation today
Motivation
With the new event this scenario can appear and we should document how we think Eiffel can describe this.
Exemplification
A best-practice/description on how Eiffel can describe a group of servers/services
Benefits
Having documentation of how we describe a group of servers/services user of Eiffel have a best-practice how to make this description.
Possible Drawbacks
None that I can think of
The text was updated successfully, but these errors were encountered: