> -----Original Message-----
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Monday, April 22, 2013 4:31 PM
> To: Tomcat Users List
> Subject: Re: two responses from one request - how is it possible ?
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Jeffrey,
> 
> On 4/22/13 4:18 PM, Jeffrey Janner wrote:
> >
> >
> >> -----Original Message----- From: André Warnier [mailto:aw@ice-
> sa.com]
> >> Sent: Sunday, April 21, 2013 7:03 PM To:
> >> Tomcat Users List Subject: Re: two responses from one request - how
> >> is it possible ?
> >>
> >> Jakub 1983 wrote:
> >>> http://www.mulesoft.com/tomcat-connector states:
> >>>
> >>> Using the current arrangement, both Connectors will pass all
> >>> requests to the same Engine, which will in turn pass all these
> >>> requests to
> >> both
> >>> of its contained web applications.  This means that each request
> >>> will potentially generate two responses, one from each application.
> >>> <Server> <Service> <Connector port="8443"/> <Connector
> port="8444"/>
> >>> <Engine> <Host name="yourhostname"> <Context path="/webapp1"/>
> >>> <Context path="/webapp2"/> </Host> </Engine> </Service> </Server>
> >>>
> >>> Is it really true what they write ?
> >>>
> >>
> >> (For anyone else reading this, I did look at the indicated webpage,
> >> and it is really what they say there)
> >>
> >> To me, it sounds like utter nonsense. Or else, I need to revise my
> >> whole understamding of HTTP and Tomcat.
> >>
> >> It even looks like nonsense squared, since :
> >>
> >> - each request is sent by one client on one connection to one port
> >> (meaning one Tomcat Connector), and the (single) response to that
> >> request will also come back on that same connection - each request
> >> should have a target URL (like /webapp1 OR /webapp2, but not both),
> >> and will be processed (once) by the application
> >> (context) corresponding to that URL, and will generate only one
> >> response
> >>
> >> Maybe we should ask the author of that page for more details.  He
> may
> >> have invented the amplifier version of Tomcat.
> >>
> >> Additionally, it is really bad practice to put <Context> elements in
> >> the server.xml file.
> >>
> >
> >> From the article:
> > " Using the current arrangement, both Connectors will pass all
> > requests to the same Engine, which will in turn pass all these
> > requests to both of its contained web applications.  This means that
> > each request will potentially generate two responses, one from each
> > application."
> >
> > Well, after noting some of the bad grammar in the opening few
> > paragraphs (listen to vs. listen on), I was going to give the author
> a
> > pass on the use of "both" in the first sentence, instead of "either"
> > or "one of".  But then he goes onto the second sentence and proves
> > that he meant both.
> >
> > In actuality, he should have stopped the first sentence at "Engine",
> > and then continued with a new sentence (keeping in mind the
> simplified
> > structure): "The Engine will then see if the first string after the
> > hostname portion of the request URL matches any of the defined
> > contexts. If a match is found, then the request is passed to that
> > context and the response is sent back via the original connector.  If
> > a match is not found, then an error is returned."
> >
> > Of course, after reading the original, I now understand why I was
> > never tempted to even try this company's version of Tomcat, despite
> > the number of times they've promoted themselves on the list.
> 
> Jason Brittain used to work at MuleSoft: they /are/ legit, though this
> particular post seems to require some serious editing, or even
> deletion.
> 
> - -chris

OH, I was never worried about /legit/ status, but this page and others probably 
made me skeptical on the quality issue.
You know, first impressions and all.  Wouldn't mind hearing from some who found 
reason to use their product over standard release.
Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to