Hi,
I am M. Nawazish. Khan. I am from India. My java.net user name is:
md.nawazish.khan
I currently work for GlobalLogic India Ltd. I was involved with Web
Application Development. However, currently I am developing Desktop
Application using JavaFX 2.2 platform. I have LinkedIn profile by the name
(it has my picture): Nawazish Mohammad Khan
Excited to get involved with the Servlet 4 and work with great people from
around the world.
- Nawazish
On Fri, Sep 26, 2014 at 7:30 AM, <users-request_at_servlet-spec.java.net>
wrote:
> Table of contents:
>
> 1. [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0 - Wenbo Zhu <wenboz_at_google.com>
> 2. [servlet-spec users] [jsr369-experts] Re: [ADMIN] Welcome to Servlet
> 4.0 - Eugene Chung(정의근) <euigeun_chung_at_tmax.co.kr>
> 3. [servlet-spec users] [jsr369-experts] Re: [ADMIN] Welcome to Servlet
> 4.0 - Mark Thomas <markt_at_apache.org>
> 4. [servlet-spec users] Request for additional TLS_UNIQUE attribute
> support from ServletRequest - Ron Monzillo <ron.monzillo_at_oracle.com>
> 5. [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0 - Greg Wilkins <gregw_at_intalio.com>
> 6. [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0 - Wenbo Zhu <wenboz_at_google.com>
>
>
>
> ---------- Forwarded message ----------
> From: Wenbo Zhu <wenboz_at_google.com>
> To: jsr369-experts_at_servlet-spec.java.net
> Cc:
> Date: Wed, 24 Sep 2014 23:56:43 -0700
> Subject: [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0
> My name is Wenbo Zhu and I represent Google and live in the Bay Area,
> California.
>
> I am responsible for Google's HTTP "Servlet" stack, in different
> languages, and is the author of Closure WebChannel (aka "WebSocket" in
> HTTP).
>
> Look forward to working you all.
>
> Cheers,
> Wenbo
>
>
>
> On Wed, Sep 24, 2014 at 2:17 PM, Stuart Douglas <sdouglas_at_redhat.com>
> wrote:
>
>> My name is Stuart Douglas and I represent Red Hat.
>>
>> I live in Australia and I work on the Wildfly application server and lead
>> the Undertow web server, which is the web server used in Wildfly.
>>
>> My java.net username is stuartdouglas.
>>
>> Stuart
>>
>>
>>
>> Edward Burns wrote:
>>
>>> Hello Volunteers,
>>>
>>> This message is sent to all members of servlet-spec, including
>>> observers, but this message is really intended for Expert Group members.
>>> Note that only JCP Expert Group (EG) members may subscribe to
>>> jsr369-experts, and therefore only EG members may post to this list.
>>>
>>> Introduction
>>>
>>> Hello and welcome to the JSR-369 Expert Group for developing version
>>> 4.0 of the Servlet specification. If you're a veteran of past Servlet
>>> JSRs, thanks for coming back again, we're very glad to have you. If
>>> you're new to Servlet spec development, welcome! We look forward to
>>> more fresh ideas. My name is Ed Burns. Shing-wai Chan and I will be
>>> your co-spec leads for this JSR.
>>>
>>> Goals
>>>
>>> As stated on our JSR [1], the primary goal of this JSR is to expose
>>> support for the upcoming IETF standard HTTP/2 to users of the Servlet
>>> API. A secondary goal is to refresh the Servlet API with to achieve
>>> compliance with new features in HTTP 1.1 as well as responding to
>>> community input. The
>>> jsr369-experts_at_servlet-spec.java.net list will be used
>>> for technical discussions in JSR-369.
>>>
>>> Getting to know each other
>>>
>>> I know some of you from previous JSRs, but others are new. I'd like
>>> for everyone to share their java.net user name. If you don't have
>>> one, please get one. We'll add everyone to the servlet-spec project.
>>> Please reply to this email, including where you live, who you
>>> represent, anything else you'd like to say and, optionally, a picture
>>> or a link to a picture of yourself.
>>>
>>> Platform
>>>
>>> Servlet 4.0 is included in the the Java EE 8 platform schedule and
>>> will depend on Java EE 8 and JavaSE 8.
>>>
>>> Rights and Responsibilities
>>>
>>> Based on lessons we've learned from past JSRs, we think it would be
>>> useful to lay out some rights and responsibilites of the JSR-369 Spec
>>> Lead and EG members.
>>>
>>> * Your rights as a JSR-369-EG member
>>>
>>> - Timely response to emails
>>>
>>> - The issues you raise get dealt with and not fall on the floor
>>>
>>> - Be informed of schedule milestones and release plans as soon as
>>> possible.
>>>
>>> - Have expectations set realistically, for example, the EG needs to
>>> be made aware that the JCP process can take a long time between
>>> when the actual spec discussion work is done, and when it is
>>> final. During that time, we are going through JCP process steps,
>>> working on the TCK and polishing the RI, writing the
>>> documentation, integrating it into the release vehicle, and
>>> qualifying it with third party products.
>>>
>>> - Have access to quality tools for distributed collaborative
>>> development. For example, the issue tracker, wiki, and shared
>>> file space at servlet-spec.java.net
>>>
>>> * Your responsibilities as an EG Member
>>>
>>> - Be active in email discussions
>>>
>>> - On the rare occasions when we specifically ask for a VOTE, such
>>> as whether or not we declare that we've hit a JCP milestone, cast
>>> one.
>>>
>>> - Conduct all email in a professional manner, no flaming
>>>
>>> - Follow email discussion guidelines in this message
>>>
>>> - Stay within the scope of the JSR
>>>
>>> - Respect the spec lead's final call on the schedule for the JSR.
>>>
>>> * Our rights as spec leads
>>>
>>> - The authority to make the final call on the schedule for the JSR,
>>> after sincerely considering EG input
>>>
>>> - The authority to make executive decisions to settle deadlocks
>>>
>>> - The authority to shut down threads that are digressions.
>>>
>>> - The authority to break up email messages into separate threads to
>>> aid discussion.
>>>
>>> * Our responsiblities as spec leads
>>>
>>> - All new discussion threads receive a response within two days
>>> from Shing-wai or I, barring planned absences.
>>>
>>> - All discussion threads managed. If appropriate, they are
>>> associated with an issue-tracker issue.
>>>
>>> - See that each discussion thread is summarized and labeled as
>>> CLOSED when the discussion is resolved.
>>>
>>> - Keep the spec document up-to-date as issues are resolved
>>>
>>> Process
>>>
>>> All official spec discussion will happen on
>>> jsr372-experts_at_servlet-spec.java.net. This list is
>>> archived at [2]. We used the archive heavily in past JSRs, so please
>>> test that you can access the archive.
>>>
>>> Please send all mail in ASCII, not HTML. If you must, non ASCII
>>> attachments are ok, but generally it's better to put that sort of
>>> thing as an attachment to an issue in the issue-tracker.
>>>
>>> As mentioned above, everyone needs a java.net user id. We'll be
>>> using
>>> the servlet-spec [3] project. We'll use the servlet-spec issue
>>> tracker for all issues [4].
>>>
>>> We may have occasional conference calls if the need arises.
>>>
>>> Reference Implementation and TCK
>>>
>>> The official reference implementation for JSR-369 is being developed
>>> out in the open on the java.net project called glassfish. The TCK
>>> will be developed by Oracle internally.
>>>
>>> Email practices
>>>
>>> We will use the following conventions, used in previous iterations of
>>> the JavaServer Faces expert groups.
>>>
>>> The subject line of All core discussion threads will be prefixed by
>>> [jsr369-experts][TargetVersion-IssueNumber-ShortName].
>>> TargetVersion is optional and is assumed to be Servletv4.0 if
>>> omitted. Having this convention covers us if we end up talking
>>> about something targeted at Servletv4.1. IssueNumber is the issue
>>> number in the servlet-spec issue tracker. ShortName is a WikiWord
>>> that enables us to look at the email subject line and quickly recall
>>> the topic of the thread. For example, Subject: "[43-XMLSchema]
>>> Status"
>>>
>>> If you want to originate a thread, send it to the EG prefixed by
>>> [NEW] in the subject line. If we see the need for an issue tracker
>>> issue, we'll put it in the issue tracker, re-subject the email to be
>>> prefixed with [IssueNumber-ShortName], and discussion will continue
>>> on that thread, NOT the thread with [NEW] in the title.
>>>
>>> Put [ADMIN] at the start of the subject line for all schedule and
>>> administrative related emails.
>>>
>>> I am open to other suggestions about how to best conduct the EG
>>> discussions over email.
>>>
>>> Next Steps
>>>
>>> As you may know, next week is JavaOne 2014. Shing-wai and I are
>>> attending, as well as Greg Wilkins.
>>>
>>> We are having a face-to-face meeting, with conference call as well,
>>> the first day of JavaOne. It is a shared meeting with the JSF EG.
>>>
>>> Date: Monday 29 September 2014
>>>
>>> Time:
>>>
>>> 14:00 San Francisco
>>>
>>> 17:00 New York
>>>
>>> 23:00 Vienna
>>>
>>> Phone number:
>>>
>>> +1 866 682 4770
>>>
>>> Conference code: 7821409
>>>
>>> Access code: 2323
>>>
>>> If you are calling in from a country other than the U.S.A., please
>>> reply to me only with the country you will be calling from and I'll
>>> hopefully have a toll-free number for you in that country.
>>>
>>> Again, welcome, and we look forward to collaborating in the coming
>>> months!
>>>
>>> Ed Burns
>>>
>>> [1] http://www.jcp.org/en/jsr/detail?id=369
>>>
>>> [2] http://java.net/projects/servlet-spec/lists/jsr369-
>>> experts/archive
>>>
>>> [3] http://servlet-spec.java.net/
>>>
>>> [4] https://java.net/jira/browse/SERVLET_SPEC/
>>>
>>>
>>>
>
>
> ---------- Forwarded message ----------
> From: "Eugene Chung(정의근)" <euigeun_chung_at_tmax.co.kr>
> To: jsr369-experts_at_servlet-spec.java.net
> Cc:
> Date: Thu, 25 Sep 2014 17:15:29 +0900
> Subject: [servlet-spec users] [jsr369-experts] Re: [ADMIN] Welcome to
> Servlet 4.0
> Greetings,
>
>
> My name is Euigeun Chung.
> But my Korean name is a little bit tricky to pronounce, so call me Eugene,
> please.
>
> I work for TmaxSoft which is located in Seongnam-si, Gyeonggi-do, South
> Korea. (near Seoul)
>
> My java.net id is 'bluewolf.chung_at_gmail.com'. I have been registered as
> an observer on the servlet-spec project.
>
>
> Best regards,
> Eugene Chung (Korean : 정의근)
>
>
>> Getting to know each other
>>
>> I know some of you from previous JSRs, but others are new. I'd like
>> for everyone to share their java.net user name. If you don't have
>> one, please get one. We'll add everyone to the servlet-spec project.
>> Please reply to this email, including where you live, who you
>> represent, anything else you'd like to say and, optionally, a picture
>> or a link to a picture of yourself.
>>
>>
>
> ---------- Forwarded message ----------
> From: Mark Thomas <markt_at_apache.org>
> To: jsr369-experts_at_servlet-spec.java.net
> Cc:
> Date: Thu, 25 Sep 2014 09:26:27 +0100
> Subject: [servlet-spec users] [jsr369-experts] Re: [ADMIN] Welcome to
> Servlet 4.0
> Hi,
>
> My java.net user name is markt_asf.
>
> I am based in the UK and I am here as individual.
>
> I've been a committer to the Apache Tomcat project for over ten years
> but I only got involved with JSRs for JavaEE 7 where I was a member of
> the Servlet, EL and WebSocket EGs.
>
> Mark
>
>
>
> ---------- Forwarded message ----------
> From: Ron Monzillo <ron.monzillo_at_oracle.com>
> To: users_at_servlet-spec.java.net
> Cc:
> Date: Thu, 25 Sep 2014 11:32:41 -0400
> Subject: [servlet-spec users] Request for additional TLS_UNIQUE attribute
> support from ServletRequest
> In addition to the attributes currently required to be supported when a
> request has been received over a secure protocol, consider adding a
> requirement that that container make the value of tls_unique availbale
> via the required to be supported (SSL) attributes.
>
> tls_unique is defined in http://tools.ietf.org/html/rfc5929
>
> Access to this value will facilitate the practice of creating cookies and
> other session identifying tokens that are bound to a specific TLS
> connection (iow, that cannot be stolen and reused outside of the
> TLS connection under which they were established and returned).
>
> The attribute could be called: javax.servlet.request.tls_unique
>
> Note that support for this attribute above JSSE will require that the
> value of verifyData as conveyed in the TLS finished handshake message
> be available from the SSLSession object.
>
> Ron
>
>
> ---------- Forwarded message ----------
> From: Greg Wilkins <gregw_at_intalio.com>
> To: jsr369-experts_at_servlet-spec.java.net
> Cc:
> Date: Fri, 26 Sep 2014 06:50:54 +1000
> Subject: [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0
> Hi all,
>
> my java.net user name is gregwilkins
>
> I split my time between Sydney Australia and Liguria Italy.
>
> I've been developing the Jetty web server since 1995 (on java 0.9!) so
> that's 19 years trying
> to get the same dang program right! Jetty has followed the servlet
> specification since 1.0, but I only got involved with the specification
> process from 2.5 onwards.
>
> I'm currently in as an Individual, but will probably soon switch to
> representing Intalio, who own Webtide, who develop Jetty and who own Mort
> Bay Consulting, which holds the copyright on Jetty and employs me. (all
> problems can be solved with another level on indirection) .
>
> cheers
>
>
> On 25 September 2014 18:26, Mark Thomas <markt_at_apache.org> wrote:
>
>> Hi,
>>
>> My java.net user name is markt_asf.
>>
>> I am based in the UK and I am here as individual.
>>
>> I've been a committer to the Apache Tomcat project for over ten years
>> but I only got involved with JSRs for JavaEE 7 where I was a member of
>> the Servlet, EL and WebSocket EGs.
>>
>> Mark
>>
>>
>
>
> --
> Greg Wilkins <gregw_at_intalio.com>
> http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that
> scales
> http://www.webtide.com advice and support for jetty and cometd.
>
>
> ---------- Forwarded message ----------
> From: Wenbo Zhu <wenboz_at_google.com>
> To: jsr369-experts_at_servlet-spec.java.net
> Cc:
> Date: Thu, 25 Sep 2014 14:19:39 -0700
> Subject: [servlet-spec users] [jsr369-experts] Re: Re: [ADMIN] Welcome to
> Servlet 4.0
> Forgot to mention that my java.net id is "wenbozhu"
>
> On Wed, Sep 24, 2014 at 11:56 PM, Wenbo Zhu <wenboz_at_google.com> wrote:
>
>> My name is Wenbo Zhu and I represent Google and live in the Bay Area,
>> California.
>>
>> I am responsible for Google's HTTP "Servlet" stack, in different
>> languages, and is the author of Closure WebChannel (aka "WebSocket" in
>> HTTP).
>>
>> Look forward to working you all.
>>
>> Cheers,
>> Wenbo
>>
>>
>>
>> On Wed, Sep 24, 2014 at 2:17 PM, Stuart Douglas <sdouglas_at_redhat.com>
>> wrote:
>>
>>> My name is Stuart Douglas and I represent Red Hat.
>>>
>>> I live in Australia and I work on the Wildfly application server and
>>> lead the Undertow web server, which is the web server used in Wildfly.
>>>
>>> My java.net username is stuartdouglas.
>>>
>>> Stuart
>>>
>>>
>>>
>>> Edward Burns wrote:
>>>
>>>> Hello Volunteers,
>>>>
>>>> This message is sent to all members of servlet-spec, including
>>>> observers, but this message is really intended for Expert Group members.
>>>> Note that only JCP Expert Group (EG) members may subscribe to
>>>> jsr369-experts, and therefore only EG members may post to this list.
>>>>
>>>> Introduction
>>>>
>>>> Hello and welcome to the JSR-369 Expert Group for developing version
>>>> 4.0 of the Servlet specification. If you're a veteran of past
>>>> Servlet
>>>> JSRs, thanks for coming back again, we're very glad to have you. If
>>>> you're new to Servlet spec development, welcome! We look forward to
>>>> more fresh ideas. My name is Ed Burns. Shing-wai Chan and I will be
>>>> your co-spec leads for this JSR.
>>>>
>>>> Goals
>>>>
>>>> As stated on our JSR [1], the primary goal of this JSR is to expose
>>>> support for the upcoming IETF standard HTTP/2 to users of the Servlet
>>>> API. A secondary goal is to refresh the Servlet API with to achieve
>>>> compliance with new features in HTTP 1.1 as well as responding to
>>>> community input. The
>>>> jsr369-experts_at_servlet-spec.java.net list will be used
>>>> for technical discussions in JSR-369.
>>>>
>>>> Getting to know each other
>>>>
>>>> I know some of you from previous JSRs, but others are new. I'd like
>>>> for everyone to share their java.net user name. If you don't have
>>>> one, please get one. We'll add everyone to the servlet-spec project.
>>>> Please reply to this email, including where you live, who you
>>>> represent, anything else you'd like to say and, optionally, a picture
>>>> or a link to a picture of yourself.
>>>>
>>>> Platform
>>>>
>>>> Servlet 4.0 is included in the the Java EE 8 platform schedule and
>>>> will depend on Java EE 8 and JavaSE 8.
>>>>
>>>> Rights and Responsibilities
>>>>
>>>> Based on lessons we've learned from past JSRs, we think it would be
>>>> useful to lay out some rights and responsibilites of the JSR-369 Spec
>>>> Lead and EG members.
>>>>
>>>> * Your rights as a JSR-369-EG member
>>>>
>>>> - Timely response to emails
>>>>
>>>> - The issues you raise get dealt with and not fall on the floor
>>>>
>>>> - Be informed of schedule milestones and release plans as soon as
>>>> possible.
>>>>
>>>> - Have expectations set realistically, for example, the EG needs
>>>> to
>>>> be made aware that the JCP process can take a long time between
>>>> when the actual spec discussion work is done, and when it is
>>>> final. During that time, we are going through JCP process
>>>> steps,
>>>> working on the TCK and polishing the RI, writing the
>>>> documentation, integrating it into the release vehicle, and
>>>> qualifying it with third party products.
>>>>
>>>> - Have access to quality tools for distributed collaborative
>>>> development. For example, the issue tracker, wiki, and shared
>>>> file space at servlet-spec.java.net
>>>>
>>>> * Your responsibilities as an EG Member
>>>>
>>>> - Be active in email discussions
>>>>
>>>> - On the rare occasions when we specifically ask for a VOTE, such
>>>> as whether or not we declare that we've hit a JCP milestone,
>>>> cast
>>>> one.
>>>>
>>>> - Conduct all email in a professional manner, no flaming
>>>>
>>>> - Follow email discussion guidelines in this message
>>>>
>>>> - Stay within the scope of the JSR
>>>>
>>>> - Respect the spec lead's final call on the schedule for the JSR.
>>>>
>>>> * Our rights as spec leads
>>>>
>>>> - The authority to make the final call on the schedule for the
>>>> JSR,
>>>> after sincerely considering EG input
>>>>
>>>> - The authority to make executive decisions to settle deadlocks
>>>>
>>>> - The authority to shut down threads that are digressions.
>>>>
>>>> - The authority to break up email messages into separate threads
>>>> to
>>>> aid discussion.
>>>>
>>>> * Our responsiblities as spec leads
>>>>
>>>> - All new discussion threads receive a response within two days
>>>> from Shing-wai or I, barring planned absences.
>>>>
>>>> - All discussion threads managed. If appropriate, they are
>>>> associated with an issue-tracker issue.
>>>>
>>>> - See that each discussion thread is summarized and labeled as
>>>> CLOSED when the discussion is resolved.
>>>>
>>>> - Keep the spec document up-to-date as issues are resolved
>>>>
>>>> Process
>>>>
>>>> All official spec discussion will happen on
>>>> jsr372-experts_at_servlet-spec.java.net. This list is
>>>> archived at [2]. We used the archive heavily in past JSRs, so please
>>>> test that you can access the archive.
>>>>
>>>> Please send all mail in ASCII, not HTML. If you must, non ASCII
>>>> attachments are ok, but generally it's better to put that sort of
>>>> thing as an attachment to an issue in the issue-tracker.
>>>>
>>>> As mentioned above, everyone needs a java.net user id. We'll be
>>>> using
>>>> the servlet-spec [3] project. We'll use the servlet-spec issue
>>>> tracker for all issues [4].
>>>>
>>>> We may have occasional conference calls if the need arises.
>>>>
>>>> Reference Implementation and TCK
>>>>
>>>> The official reference implementation for JSR-369 is being developed
>>>> out in the open on the java.net project called glassfish. The TCK
>>>> will be developed by Oracle internally.
>>>>
>>>> Email practices
>>>>
>>>> We will use the following conventions, used in previous iterations of
>>>> the JavaServer Faces expert groups.
>>>>
>>>> The subject line of All core discussion threads will be prefixed by
>>>> [jsr369-experts][TargetVersion-IssueNumber-ShortName].
>>>> TargetVersion is optional and is assumed to be Servletv4.0 if
>>>> omitted. Having this convention covers us if we end up talking
>>>> about something targeted at Servletv4.1. IssueNumber is the issue
>>>> number in the servlet-spec issue tracker. ShortName is a WikiWord
>>>> that enables us to look at the email subject line and quickly
>>>> recall
>>>> the topic of the thread. For example, Subject: "[43-XMLSchema]
>>>> Status"
>>>>
>>>> If you want to originate a thread, send it to the EG prefixed by
>>>> [NEW] in the subject line. If we see the need for an issue tracker
>>>> issue, we'll put it in the issue tracker, re-subject the email to
>>>> be
>>>> prefixed with [IssueNumber-ShortName], and discussion will continue
>>>> on that thread, NOT the thread with [NEW] in the title.
>>>>
>>>> Put [ADMIN] at the start of the subject line for all schedule and
>>>> administrative related emails.
>>>>
>>>> I am open to other suggestions about how to best conduct the EG
>>>> discussions over email.
>>>>
>>>> Next Steps
>>>>
>>>> As you may know, next week is JavaOne 2014. Shing-wai and I are
>>>> attending, as well as Greg Wilkins.
>>>>
>>>> We are having a face-to-face meeting, with conference call as well,
>>>> the first day of JavaOne. It is a shared meeting with the JSF EG.
>>>>
>>>> Date: Monday 29 September 2014
>>>>
>>>> Time:
>>>>
>>>> 14:00 San Francisco
>>>>
>>>> 17:00 New York
>>>>
>>>> 23:00 Vienna
>>>>
>>>> Phone number:
>>>>
>>>> +1 866 682 4770
>>>>
>>>> Conference code: 7821409
>>>>
>>>> Access code: 2323
>>>>
>>>> If you are calling in from a country other than the U.S.A., please
>>>> reply to me only with the country you will be calling from and I'll
>>>> hopefully have a toll-free number for you in that country.
>>>>
>>>> Again, welcome, and we look forward to collaborating in the coming
>>>> months!
>>>>
>>>> Ed Burns
>>>>
>>>> [1] http://www.jcp.org/en/jsr/detail?id=369
>>>>
>>>> [2] http://java.net/projects/servlet-spec/lists/jsr369-
>>>> experts/archive
>>>>
>>>> [3] http://servlet-spec.java.net/
>>>>
>>>> [4] https://java.net/jira/browse/SERVLET_SPEC/
>>>>
>>>>
>>>>
>>
>
> End of digest for list users_at_servlet-spec.java.net - Fri, 26 Sep 2014
>
>