Skip to content
New issue

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

Open google doc issue 24: RSpec negociation #33

Open
wvdemeer opened this issue May 15, 2014 · 0 comments
Open

Open google doc issue 24: RSpec negociation #33

wvdemeer opened this issue May 15, 2014 · 0 comments

Comments

@wvdemeer
Copy link

Below is a literal copy of google doc issue 14:

  1. RSpec negociation -- simple mechanism, list of rspecs -> let the AM put them in the right order from most information to least information

Jordan: In the current GetVersion() metadata, a client cannot find enough information about the prefered RSpec format to choose, that will lead to the maximum amount of information. For example, let’s take the example of the IoTLAB testbed that has extended PlanetLab RSpecs to add x,y,z coordinates for its nodes. The AM will advertise support for both its own RSpecs and PLE RSpecs. A client might want to negociate the RSpec to use by first selecting the RSpecs both the client and the server can talk, then selecting among the common RSpecs the one that bring the maximum amount of information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant