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

Tracking Issue for Server Attributes being Experimental. #1710

Open
carl-mastrangelo opened this issue Apr 21, 2016 · 2 comments
Open

Tracking Issue for Server Attributes being Experimental. #1710

carl-mastrangelo opened this issue Apr 21, 2016 · 2 comments
Labels
experimental API Issue tracks stabilizing an experimental API P3
Milestone

Comments

@carl-mastrangelo
Copy link
Contributor

Other languages propagate these via a context, maybe they should be done that way? In any case, these should be looked at to see if they are part of 1.0.

@carl-mastrangelo carl-mastrangelo added this to the 1.0 milestone Apr 21, 2016
@hsaliak hsaliak added the P3 label Apr 26, 2016
@carl-mastrangelo carl-mastrangelo changed the title Server.REMOTE_ADDR_KEY and SSL_SESSION_KEY should be checked to see if still experimental. Tracking Issue for Server Attributes being Experimental. May 3, 2016
@carl-mastrangelo
Copy link
Contributor Author

Specific usages:

  • ServerCall.REMOTE_ADDR_KEY
  • ServerCall.SSL_SESSION_KEY

@ejona86 ejona86 modified the milestones: 1.1, 1.0 May 23, 2016
@louiscryan
Copy link
Contributor

No need to resolve for 1.0, current usage is low.

@ejona86 ejona86 modified the milestones: Unscheduled, 1.1 Aug 9, 2016
@ejona86 ejona86 added the experimental API Issue tracks stabilizing an experimental API label Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experimental API Issue tracks stabilizing an experimental API P3
Projects
None yet
Development

No branches or pull requests

4 participants