| Re: has anyone used multithreaded PHP appserver.io for application? [message #183414 is a reply to message #183412] |
Wed, 23 October 2013 18:09   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 10/23/2013 1:54 PM, Arno Welzel wrote:
> Jerry Stuckle, 2013-10-22 22:03:
>
> [...]
>> No, Tomcat and Geronimo are servers for specific applications.
>
> Sorry - but Tomcat and Geronimo are *not* different servers. At least
> you should read my references or just admit, that you don't know every
> product in the world.
>
> And concerning "specific applications" - this is really a very general
> conclusion. Apache HTTP Server (and nginx, Microsoft IIS etc.) is also a
> server for specific applications and there are many applications where
> an Apache HTTP Server just does not really fit in. Yeah - you can
> develop a module for everything - but developing modules for Apache HTTP
> Server is not always the smartest solution.
>
> Apache HTTP Server is quite good in serving web pages - but it does not
> provide a framework which you need for certain applications
> (persistance, session management etc.), since this is not its main purpose.
>
> Of course - you can add all this using modules - but if this is enough
> for you to call something an "application server" then your
> understanding of "application server" is quite broad... even using a C++
> compiler or a PHP runtime it is possible to create something which
> serves applications without any other software at all - but even you
> would not call a C++ compiler or PHP an "application server".
>
>> You don't understand all of the capabilities of Apache if you don't
>> understand it can also serve applications.
>
> Did I ever question this? It was just about how to define something an
> "application server".
>
>> Sure, it's *main* purpose is as a webserver. But it can do so much
>> more, with the appropriate modules.
>
> Yep - it's *main* purpose is a webserver and Apache HTTP Server can
> *also* be extended to serve applications. But some severs are more
> tailored to this specific needs and therefore usually called
> "application server".
>
> Do you know the saying "if all you have is a hammer, everything looks
> like a nail" - maybe you understand now what I mean? I don't have a
> problem with Apache HTTP Server - I use it every day and of course I
> know about Apache modules as well. But my daily business is not just
> using Apache with modules - maybe yours is.
>
>
This "response" is so full of holes it's not even worth a response. But
that's what I've come to expect from you, Arno. You're right about
everything, even when you have no idea what you're talking about (as
here). And everyone else is wrong.
For your information, I was working with application servers way back in
the 80's - long before the internet became popular. Unlike you, I DO
know what an application server is. And unlike you, I DO know how to
set up Apache as an application server. You obviously don't, so you
claim it can't be done. You haven't even researched it, have you? Not
that it matters - you would just claim whomever posted the information
you disagree with is wrong, also.
I'm outta here, troll.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]