Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #11426 > unrolled thread
| Started by | Nay Min <nwinhart@gmail.com> |
|---|---|
| First post | 2013-10-14 07:38 -0700 |
| Last post | 2013-10-21 05:48 -0700 |
| Articles | 20 on this page of 22 — 7 participants |
Back to article view | Back to comp.lang.php
has anyone used multithreaded PHP appserver.io for application? Nay Min <nwinhart@gmail.com> - 2013-10-14 07:38 -0700
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-14 20:43 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-20 16:35 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-20 10:40 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-20 21:00 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-20 21:00 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-21 11:44 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-21 08:02 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-21 14:20 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-21 09:05 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-21 16:37 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-21 11:02 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-22 05:37 +0200
Re: has anyone used multithreaded PHP appserver.io for application? stefan.willkommer@googlemail.com - 2013-10-22 07:48 -0700
Re: has anyone used multithreaded PHP appserver.io for application? The Natural Philosopher <tnp@invalid.invalid> - 2013-10-22 16:00 +0100
Re: has anyone used multithreaded PHP appserver.io for application? Evan Platt <evan@theobvious.espphotography.com.invalid> - 2013-10-22 09:01 -0700
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-22 16:03 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-23 19:54 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-23 14:09 -0400
Re: has anyone used multithreaded PHP appserver.io for application? Arno Welzel <usenet@arnowelzel.de> - 2013-10-23 22:09 +0200
Re: has anyone used multithreaded PHP appserver.io for application? Nay Min <nwinhart@gmail.com> - 2013-10-21 03:25 -0700
Re: has anyone used multithreaded PHP appserver.io for application? Scott Johnson <noonehome@chalupasworld.com> - 2013-10-21 05:48 -0700
Page 1 of 2 [1] 2 Next page →
| From | Nay Min <nwinhart@gmail.com> |
|---|---|
| Date | 2013-10-14 07:38 -0700 |
| Subject | has anyone used multithreaded PHP appserver.io for application? |
| Message-ID | <ba99cf9b-d2de-4f2a-9c8d-9219b0b399b8@googlegroups.com> |
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
[toc] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-14 20:43 -0400 |
| Message-ID | <l3i335$afl$1@dont-email.me> |
| In reply to | #11426 |
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. And no way a server written in a scripting language such as PHP loads faster than a compiled C program such as Apache. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-20 16:35 +0200 |
| Message-ID | <5263EA48.9000103@arnowelzel.de> |
| In reply to | #11430 |
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-application-server-php-written-php/> <http://thestartuppitch.com/pitches/pitch-for-appserver-io/> -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-20 10:40 -0400 |
| Message-ID | <l40q1h$sed$1@dont-email.me> |
| In reply to | #11482 |
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-application-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. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-20 21:00 +0200 |
| Message-ID | <52642865.4010407@arnowelzel.de> |
| In reply to | #11483 |
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-application-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". -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-20 21:00 -0400 |
| Message-ID | <l41uah$6uc$1@dont-email.me> |
| In reply to | #11499 |
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-application-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. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-21 11:44 +0200 |
| Message-ID | <5264F77F.9040908@arnowelzel.de> |
| In reply to | #11505 |
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-application-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++? -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-21 08:02 -0400 |
| Message-ID | <l43559$k5a$1@dont-email.me> |
| In reply to | #11519 |
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-application-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 definition of a network resource - of which an application is one type of resource. And ANY application server passes requests to various applications. It doesn't do the work itself. But I see you don't understand how an application server works. It figures. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-21 14:20 +0200 |
| Message-ID | <52651BFB.1070608@arnowelzel.de> |
| In reply to | #11524 |
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-application-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
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-21 09:05 -0400 |
| Message-ID | <l438rd$8r6$2@dont-email.me> |
| In reply to | #11527 |
On 10/21/2013 8:20 AM, Arno Welzel wrote: > 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-application-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 ;-) > You don't know the difference, do you? It figures. >> 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". > An application server does not "do the work itself" either. But you obviously don't understand what an application server does. >> 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. > > Then your boss needs to find someone who knows what they are talking about. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-21 16:37 +0200 |
| Message-ID | <52653C28.9010600@arnowelzel.de> |
| In reply to | #11530 |
Am 21.10.2013 15:05, schrieb Jerry Stuckle: > On 10/21/2013 8:20 AM, Arno Welzel wrote: >> 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: [...] ["Apache HTTP Server is an 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 ;-) >> > > You don't know the difference, do you? It figures. Do you? Is there any difference for you? Well - then even PHP is a web server and an application server as well, since it can be used to serve web pages and run applications without Apache at all ;-) [...] >>> 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. >> >> > > Then your boss needs to find someone who knows what they are talking about. ROTFL Go ahead - enlighten us with your knowledge. Maybe some URL with further information about the concepts of "application servers"? ;-) -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-21 11:02 -0400 |
| Message-ID | <l43fla$hlq$1@dont-email.me> |
| In reply to | #11533 |
On 10/21/2013 10:37 AM, Arno Welzel wrote: > Am 21.10.2013 15:05, schrieb Jerry Stuckle: > >> On 10/21/2013 8:20 AM, Arno Welzel wrote: >>> 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: > [...] > > ["Apache HTTP Server is an 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 ;-) >>> >> >> You don't know the difference, do you? It figures. > > Do you? Is there any difference for you? > > Well - then even PHP is a web server and an application server as well, > since it can be used to serve web pages and run applications without > Apache at all ;-) > Which just shows you have absolutely no idea what an application server is. > [...] >>>> 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. >>> >>> >> >> Then your boss needs to find someone who knows what they are talking about. > > ROTFL > > Go ahead - enlighten us with your knowledge. Maybe some URL with further > information about the concepts of "application servers"? ;-) > > Nope. I don't feed trolls. Now why don't you just crawl back under a bridge? This newsgroup has been so much nicer when you aren't around. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-22 05:37 +0200 |
| Message-ID | <5265F2FF.3060900@arnowelzel.de> |
| In reply to | #11534 |
Jerry Stuckle, 2013-10-21 17:02: > On 10/21/2013 10:37 AM, Arno Welzel wrote: >> Am 21.10.2013 15:05, schrieb Jerry Stuckle: >> >>> On 10/21/2013 8:20 AM, Arno Welzel wrote: >>>> 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: >> [...] >> >> ["Apache HTTP Server is an 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 ;-) >>>> >>> >>> You don't know the difference, do you? It figures. >> >> Do you? Is there any difference for you? >> >> Well - then even PHP is a web server and an application server as well, >> since it can be used to serve web pages and run applications without >> Apache at all ;-) >> > > Which just shows you have absolutely no idea what an application server is. And your reaction shows you have no idea what a smiley is ;-) -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | stefan.willkommer@googlemail.com |
|---|---|
| Date | 2013-10-22 07:48 -0700 |
| Message-ID | <4402c9a9-e612-45be-9a5c-106463117a98@googlegroups.com> |
| In reply to | #11541 |
Am Dienstag, 22. Oktober 2013 05:37:35 UTC+2 schrieb Arno Welzel: > Jerry Stuckle, 2013-10-21 17:02: > > > > > On 10/21/2013 10:37 AM, Arno Welzel wrote: > > >> Am 21.10.2013 15:05, schrieb Jerry Stuckle: > > >> > > >>> On 10/21/2013 8:20 AM, Arno Welzel wrote: > > >>>> 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: > > >> [...] > > >> > > >> ["Apache HTTP Server is an 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 ;-) > > >>>> > > >>> > > >>> You don't know the difference, do you? It figures. > > >> > > >> Do you? Is there any difference for you? > > >> > > >> Well - then even PHP is a web server and an application server as well, > > >> since it can be used to serve web pages and run applications without > > >> Apache at all ;-) > > >> > > > > > > Which just shows you have absolutely no idea what an application server is. > > > > And your reaction shows you have no idea what a smiley is ;-) > > > > > > > > -- > > Arno Welzel > > http://arnowelzel.de > > http://de-rec-fahrrad.de It seems that we went a bit off topic here or should I say more in a debate of principles. In this case I want to second the opinion of Arno with the following link to wikipedia http://en.wikipedia.org/wiki/Application_server It clarifies what an application server is and what it provides and sorry Jerry but the Apache Webserver as the name says is a webserver that's why they built some other projects like Tomcat and Geronimo which are Servlet Containers or in case of Geronimo real application servers. cheers, Stefan from the appserver.io team
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2013-10-22 16:00 +0100 |
| Message-ID | <l463v1$la9$1@news.albasani.net> |
| In reply to | #11542 |
On 22/10/13 15:48, stefan.willkommer@googlemail.com wrote: > It seems that we went a bit off topic here or should I say more in a > debate of principles. In this case I want to second the opinion of > Arno with the following link to wikipedia > http://en.wikipedia.org/wiki/Application_server It clarifies what an > application server is and what it provides and sorry Jerry but the > Apache Webserver as the name says is a webserver that's why they > built some other projects like Tomcat and Geronimo which are Servlet > Containers or in case of Geronimo real application servers. > Jerry has a minumental talent for redefining terms he has used incorrectly, in order to claim that after all, he didnt. I see no need to apologise to him. I have never seen hm apologise to anyone he has wrongly abused online. Ther are those who consider him an anal orifice, but in fact he more resembles a vagina. > cheers, Stefan > > from the appserver.io team > -- Ineptocracy (in-ep-toc’-ra-cy) – a system of government where the least capable to lead are elected by the least capable of producing, and where the members of society least likely to sustain themselves or succeed, are rewarded with goods and services paid for by the confiscated wealth of a diminishing number of producers.
[toc] | [prev] | [next] | [standalone]
| From | Evan Platt <evan@theobvious.espphotography.com.invalid> |
|---|---|
| Date | 2013-10-22 09:01 -0700 |
| Message-ID | <n98d69d97oecgklf7a5aoiecur8775buuc@4ax.com> |
| In reply to | #11543 |
On Tue, 22 Oct 2013 16:00:48 +0100, The Natural Philosopher <tnp@invalid.invalid> wrote: >Jerry has a minumental talent for redefining terms he has used >incorrectly, in order to claim that after all, he didnt. > >I see no need to apologise to him. > >I have never seen hm apologise to anyone he has wrongly abused online. > >Ther are those who consider him an anal orifice, but in fact he more >resembles a vagina. Glad I'm not the only one who feels that way about him. I should have plonked him a long time ago. -- To reply via e-mail, remove The Obvious and .invalid from my e-mail address.
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-22 16:03 -0400 |
| Message-ID | <l46llo$qjo$2@dont-email.me> |
| In reply to | #11542 |
On 10/22/2013 10:48 AM, stefan.willkommer@googlemail.com wrote: > Am Dienstag, 22. Oktober 2013 05:37:35 UTC+2 schrieb Arno Welzel: >> Jerry Stuckle, 2013-10-21 17:02: >> >> >> >>> On 10/21/2013 10:37 AM, Arno Welzel wrote: >> >>>> Am 21.10.2013 15:05, schrieb Jerry Stuckle: >> >>>> >> >>>>> On 10/21/2013 8:20 AM, Arno Welzel wrote: >> >>>>>> 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: >> >>>> [...] >> >>>> >> >>>> ["Apache HTTP Server is an 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 ;-) >> >>>>>> >> >>>>> >> >>>>> You don't know the difference, do you? It figures. >> >>>> >> >>>> Do you? Is there any difference for you? >> >>>> >> >>>> Well - then even PHP is a web server and an application server as well, >> >>>> since it can be used to serve web pages and run applications without >> >>>> Apache at all ;-) >> >>>> >> >>> >> >>> Which just shows you have absolutely no idea what an application server is. >> >> >> >> And your reaction shows you have no idea what a smiley is ;-) >> >> >> >> >> >> >> >> -- >> >> Arno Welzel >> >> http://arnowelzel.de >> >> http://de-rec-fahrrad.de > > It seems that we went a bit off topic here or should I say more in a debate of principles. In this case I want to second the opinion of Arno with the following link to wikipedia http://en.wikipedia.org/wiki/Application_server It clarifies what an application server is and what it provides and sorry Jerry but the Apache Webserver as the name says is a webserver that's why they built some other projects like Tomcat and Geronimo which are Servlet Containers or in case of Geronimo real application servers. > > cheers, > Stefan > > from the appserver.io team > No, Tomcat and Geronimo are servers for specific applications. You don't understand all of the capabilities of Apache if you don't understand it can also serve applications. Sure, it's *main* purpose is as a webserver. But it can do so much more, with the appropriate modules. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-23 19:54 +0200 |
| Message-ID | <52680D5B.2020304@arnowelzel.de> |
| In reply to | #11546 |
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. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Date | 2013-10-23 14:09 -0400 |
| Message-ID | <l493bp$6bs$1@dont-email.me> |
| In reply to | #11554 |
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@attglobal.net ==================
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2013-10-23 22:09 +0200 |
| Message-ID | <52682D08.9040400@arnowelzel.de> |
| In reply to | #11556 |
Jerry Stuckle, 2013-10-23 20:09: [Fullquote deleted - is this really neccessary?] > This "response" is so full of holes it's not even worth a response. But Which holes? Can you name at least one? Can you show me where I'm wrong in my knowledge about Apache Geronimo and that Tomcat is not just a different server besides Geronimo? > 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. As I know you... no details and no *specific* critics, just a generic "you don't know what you are talking about"... > 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 If you want to say I wouldn't respect your age and experience - you're wrong. This was not the point and I apologize if you got it wrong. > 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 Me too - so what? > claim it can't be done. You haven't even researched it, have you? Not Where exactly did I claim that Apache HTTP Server can not be used to serve applications? I never questioned, that Apache HTTP Servers can be used like this - I just asked how *YOU* define "application server" since I don't agree with "applications are just another URI" - this is way to simplified. You could have answered, that "application server" is a concept and not just a software and also post some references for further information, so others could learn something as well. But no - instead you rely on your big ego. If you say something everybody else will just have to take this for granted like "Applications are just another URI. Apache can server applications just as easily as it can server web pages." - and that's it - perdiod. If Jerry Stuckle says this, it has to be like that and no further discussion about the topic "what are application servers and why are there different Apache projects to deal with different needs". And you tell ME that I assume "everybody else is wrong", if a say something. Remember of <stefan.willkommer@googlemail.com>? He didn't agree to you as well. Of course you will see this as an irrelevant post by someone who does not know anything about this topic as well - don't you? And I already mentioned in <5264F77F.9040908@arnowelzel.de> that I asked YOU if YOU mean using MODULES in APACHE by "using Apache HTTP Server as application server". BTW - I also use Phusion Passenger for some of our applications besides the PHP stuff. And your answer to this was: "But I see you don't understand how an application server works. It figures." And in <l46llo$qjo$2@dont-email.me> you even confirmed my assumption: "You don't understand all of the capabilities of Apache if you don't understand it can also serve applications. Sure, it's *main* purpose is as a webserver. But it can do so much more, with the appropriate modules." > that it matters - you would just claim whomever posted the information > you disagree with is wrong, also. Where exactly did I say anything like this? Where exactly did I disagree, that Apache can be used to serve applications using modules? > I'm outta here, troll. As all this is already WAY off topic - F'Up to poster if you really want to discuss opinions. For me end of public discussion here - if you want to go on, send me an e-mail or let it be. I apoloogize for bringing so much noise in here - but to be honest you must admit, that you are also a bit stubborn in way ;-) -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | comp.lang.php
csiph-web