On 07/03/18 12:02, Sen, Anurag wrote:
>
>
>> -Original Message-
>> From: Mark Thomas [mailto:ma...@apache.org]
>> Sent: 07 March 2018 17:17
>> To: users@tomcat.apache.org
>> Subject: Re: [Tomcat Custom Connector]Private Fields in NIOEndpoint class
&g
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: 07 March 2018 17:17
> To: users@tomcat.apache.org
> Subject: Re: [Tomcat Custom Connector]Private Fields in NIOEndpoint class
>
> On 07/03/2018 11:05, Sen, Anurag wrote:
> > Agreed
On 07/03/2018 11:05, Sen, Anurag wrote:
Agreed, that Endpoint is protocol agnostic. My query was more in concern with
the endpoint implementations being so encapsulated, that it leaves very little
scope to extend tomcat endpoints(without actually copy-pasting the code into
the custom endpoint)
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: 07 March 2018 14:54
> To: Tomcat Users List
> Subject: Re: [Tomcat Custom Connector]Private Fields in NIOEndpoint class
>
> On 07/03/18 09:03, Sen, Anurag wrote:
> > Dear Tomcat u
On 07/03/18 09:03, Sen, Anurag wrote:
> Dear Tomcat users/dev team,
>
> I am working on porting an enterprise application from Tomcat 4.x to Tomcat
> 8.5.x.
>
> Probably you can throw some light on the problem I am facing.
> The application that I am porting has a custom protocol(inheriting
> H
Dear Tomcat users/dev team,
I am working on porting an enterprise application from Tomcat 4.x to Tomcat
8.5.x.
Probably you can throw some light on the problem I am facing.
The application that I am porting has a custom protocol(inheriting
HTTP11NIOProtocol) and custom endpoint(inheriting NIOEn
