Very interesting!
Yes, managed code is the path to follow.
First idea non-blocking IO (from C# client side): use the new async/await
for the communication. But force to use the new .NET framework and Visual
Studio. And await is a wait on the current threads:
Hi Angel and Bilal,
thank you for your replies.
-Original Message-
From: Angel Java Lopez [mailto:ajlopez2...@gmail.com]
Sent: Saturday, February 15, 2014 11:59 AM
To: Tomcat Users List
Subject: Re: Status of the current IIS ISAPI Redirector for Tomcat
Very interesting!
Yes
supports TLS/NPM?
*gruss*
Martin
__
From: kpreis...@apache.org
To: users@tomcat.apache.org
Subject: RE: Status of the current IIS ISAPI Redirector for Tomcat
Date: Sat, 15 Feb 2014 15:00:44 +0100
Hi Angel and Bilal,
thank you for your
Konstantin,
On Fri, Jan 24, 2014 at 2:06 PM, Konstantin Preißer kpreis...@apache.orgwrote:
Hi all,
for my Java Servlet web applications which run on Tomcat (currently
8.0.0-RC 10) on various Windows Server OSes (currently Windows Server 2012
R2), I use the ISAPI Redirector to forward
Hi all,
for my Java Servlet web applications which run on Tomcat (currently 8.0.0-RC
10) on various Windows Server OSes (currently Windows Server 2012 R2), I use
the ISAPI Redirector to forward requests from IIS to Tomcat over AJP. I use IIS
as primary web server because I also host other
