(2nd round) Proposed API Changes for JEP 114: TLS Server Name Indication (SNI) Extension (original) (raw)
Sean Mullan sean.mullan at oracle.com
Fri Aug 10 15:13:33 UTC 2012
- Previous message (by thread): (2nd round) Proposed API Changes for JEP 114: TLS Server Name Indication (SNI) Extension
- Next message (by thread): (2nd round) Proposed API Changes for JEP 114: TLS Server Name Indication (SNI) Extension
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8/9/12 12:04 PM, Xuelei Fan wrote:
The new webrev: http://cr.openjdk.java.net./~xuelei/7068321/webrevspec.02/
Diffs from the previous webrev: 1. changed the method names setServername->setAccessibleServerName getServername->getAccessibleServerNames setServernamePattern->setRecognizableServername getServernamePatterns->getRecognizableServernames
FWIW, I prefer the previous names. The terms "Accessible" and "Recognizable" are a bit awkward. I like the short, simple method names for the client side (get/setServerName) and having the Pattern name in the server method more clearly indicates that this is for matching server names.
--Sean
- Previous message (by thread): (2nd round) Proposed API Changes for JEP 114: TLS Server Name Indication (SNI) Extension
- Next message (by thread): (2nd round) Proposed API Changes for JEP 114: TLS Server Name Indication (SNI) Extension
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]