| Re: has anyone used multithreaded PHP appserver.io for application? [message #183373 is a reply to message #183370] |
Mon, 21 October 2013 12:20   |
Arno Welzel
Messages: 317
Registered: October 2011
Karma:
|
Senior Member |
|
|
Am 21.10.2013 14:02, schrieb Jerry Stuckle:
> On 10/21/2013 5:44 AM, Arno Welzel wrote:
>> Am 21.10.2013 03:00, schrieb Jerry Stuckle:
>>> On 10/20/2013 3:00 PM, Arno Welzel wrote:
>>>> Jerry Stuckle, 2013-10-20 16:40:
>>>>
>>>> > On 10/20/2013 10:35 AM, Arno Welzel wrote:
>>>> >> Jerry Stuckle, 2013-10-15 02:43:
>>>> >>
>>>> >>> On 10/14/2013 10:38 AM, Nay Min wrote:
>>>> >>>> Hi Php Developer,
>>>> >>>>
>>>> >>>> I like to know has anyone already use opensource appserver.io multithread Php server, it sound like we do not need #nginx #apache server anymore and faster load time.
>>>> >>>>
>>>> >>>> Regards,
>>>> >>>> Nay Min
>>>> >>>>
>>>> >>>
>>>> >>> Nope, but then my Apache servers do a lot more than just load PHP pages.
>>>> >>
>>>> >> Seems you don't know the difference between an application server and a
>>>> >> web server. Anyway - appserver.io also does a lot more than just loading
>>>> >> PHP scripts. At least it sounds promising - a bit like Ruby on Rails in
>>>> >> PHP ;-)
>>>> >>
>>>> >> Also see:
>>>> >>
>>>> >> <http://www.sitepoint.com/interview-appserver-io-crew/>
>>>> >> < http://www.dev-metal.com/postmodern-php-appserver-io-multithreaded-applicat ion-server-php-written-php/>
>>>> >> <http://thestartuppitch.com/pitches/pitch-for-appserver-io/>
>>>> >>
>>>> >>
>>>> >
>>>> > No, I'm not mixing them up. But Apache can also be used as an
>>>> > application server - and much more efficiently. It does a lot more than
>>>> > just load PHP pages.
>>>>
>>>> The only application server I know in the context of Apache is Geronimo
>>>> (<http://geronimo.apache.org/>) including Tomcat. Maybe you should
>>>> clarify what you mean by "application server".
>>>>
>>>>
>>>
>>> Applications are just another URI. Apache can server applications just
>>> as easily as it can server web pages.
>>
>> "Applications are just another URI"... that's your definition of
>> "application server"? I see.
>>
>> And by "serving applications" you mean using Apache to pass requests to
>> PHP, Tomcat, Phusion Passenger etc. or building your own modules in C/C++?
>>
>>
>>
>
> No, that is not MY definition of an application server. That is the
Ok - it was the answer of my request to clarify your(!) understanding of
"application server".
> definition of a network resource - of which an application is one type
> of resource.
I see. In this case every system able to handle network request is an
"application server". Interesting - I wonder why the guys at Apache
spend time in maintaining Axis, Tomcat etc. if Apache itself is an
application server already ;-)
> And ANY application server passes requests to various applications. It
> doesn't do the work itself.
Of course the Apache HTTP server does not do the work itself - that's
why it is called a "web server" and not "application server".
> But I see you don't understand how an application server works. It figures.
I do - it's part of my job. And no - I am not limited to C, C++, PHP and
SQL and Apache. But I do distinguish between Apache as a WEB SERVER and
OTHER servers as APPLICATION SERVER.
--
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]