Emile van Sebille wrote:
> You're missing the point -- set-up and tear-down overhead is involved
> for both python and php cgi based web serving, and Bruno I'm sure would
> concur that python in this suffers similarly.
Well I wrote, "Each has its distinguishing features -- how efficiently
a web ap
On 4/21/2010 11:37 AM Bryan said...
'Round here we love Python. I prefer Python to Perl or PHP even in
those languages' particular areas of specialization. Advocating for
Python does not require spreading myths about PHP.
You're missing the point -- set-up and tear-down overhead is involved
fo
Bruno Desthuilliers wrote:
> Bryan a écrit :
>
> > Bruno Desthuilliers wrote:
> >> Nope. I want to keep all my settings parsed, my librairies loaded, all
> >> my connections opened etc. That is, all the time consuming stuff at app
> >> startup - which, with PHP, mostly happens for each and every re
On 04/21/2010 08:46 AM, Bruno Desthuilliers wrote:
Bryan a écrit :
Bruno Desthuilliers wrote:
Many large, sopĥisticated etc applications are written in C. Does that
make C a practical application programming language ?
It's at least a strong clue.
Oh, yes ? Then why don't you use C for web
Bryan a écrit :
Bruno Desthuilliers wrote:
Nope. I want to keep all my settings parsed, my librairies loaded, all
my connections opened etc. That is, all the time consuming stuff at app
startup - which, with PHP, mostly happens for each and every request.
O.K. I wasn't clear on your objection.
Bruno Desthuilliers wrote:
> Nope. I want to keep all my settings parsed, my librairies loaded, all
> my connections opened etc. That is, all the time consuming stuff at app
> startup - which, with PHP, mostly happens for each and every request.
O.K. I wasn't clear on your objection. As I said the
On Wed, Apr 21, 2010 at 2:33 AM, Adam Tauno Williams
wrote:
> On Wed, 2010-04-21 at 10:28 +0200, Bruno Desthuilliers wrote:
>> Bryan a écrit :
>> >
>> > I think I see what you mean
>>
>> Err...
>>
>> > -- correct me if I'm wrong:
>>
>> You are, sorry !-)
>>
>> > You want to
>> > keep complex appli
Bruno Desthuilliers writes:
> Nope. I want to keep all my settings parsed, my librairies loaded, all
> my connections opened etc. That is, all the time consuming stuff at
> app startup - which, with PHP, mostly happens for each and every
> request.
I thought we have WSGI for this? Nothing stops
On Wed, 2010-04-21 at 10:28 +0200, Bruno Desthuilliers wrote:
> Bryan a écrit :
> >
> > I think I see what you mean
>
> Err...
>
> > -- correct me if I'm wrong:
>
> You are, sorry !-)
>
> > You want to
> > keep complex application data structures around between requests.
>
> Nope. I want to
Bryan a écrit :
I think I see what you mean
Err...
-- correct me if I'm wrong:
You are, sorry !-)
You want to
keep complex application data structures around between requests.
Nope. I want to keep all my settings parsed, my librairies loaded, all
my connections opened etc. That is, al
Bruno wrote:
> Bryan a écrit :
> > I think you guys got some incorrect info about PHP. A variety of
> > execution options are available, such as FastCGI and in-server
> > modules.
>
> mod_php, yes, but that doesn't change anything to the fact that it has
> to rebuild the whole world on each and eve
On Tue, 2010-04-20 at 17:05 +0200, Bruno Desthuilliers wrote:
> Adam Tauno Williams a écrit :
> > On Mon, 2010-04-19 at 15:15 +0200, Bruno Desthuilliers wrote:
> >> Gilles Ganault a écrit :
> >>> On Thu, 15 Apr 2010 12:41:56 +0200, Bruno Desthuilliers
> >>> wrote:
> The PHP execution model (m
Adam Tauno Williams a écrit :
On Mon, 2010-04-19 at 15:15 +0200, Bruno Desthuilliers wrote:
Gilles Ganault a écrit :
On Thu, 15 Apr 2010 12:41:56 +0200, Bruno Desthuilliers
wrote:
The PHP execution model (mostly based on CGI FWIW) tends to be a bit
unpractical for non-trivial applications sin
Bryan a écrit :
Bruno Desthuilliers wrote:
Gilles Ganault a écrit :
Apart from the ease of having the application run at all times, I'd be
curious to read about an application that was written in PHP and then
a long-running process and see if performance improved.
I'm not sure there's a way to
On Mon, 2010-04-19 at 15:15 +0200, Bruno Desthuilliers wrote:
> Gilles Ganault a écrit :
> > On Thu, 15 Apr 2010 12:41:56 +0200, Bruno Desthuilliers
> > wrote:
> >> The PHP execution model (mostly based on CGI FWIW) tends to be a bit
> >> unpractical for non-trivial applications since you have to
Bruno Desthuilliers wrote:
> Gilles Ganault a écrit :
> > Apart from the ease of having the application run at all times, I'd be
> > curious to read about an application that was written in PHP and then
> > a long-running process and see if performance improved.
>
> I'm not sure there's a way to do
Gilles Ganault a écrit :
On Thu, 15 Apr 2010 12:41:56 +0200, Bruno Desthuilliers
wrote:
The PHP execution model (mostly based on CGI FWIW) tends to be a bit
unpractical for non-trivial applications since you have to rebuild the
whole world for each and any incoming request, while with a long-r
On Thu, 15 Apr 2010 12:41:56 +0200, Bruno Desthuilliers
wrote:
>The PHP execution model (mostly based on CGI FWIW) tends to be a bit
>unpractical for non-trivial applications since you have to rebuild the
>whole world for each and any incoming request, while with a long-running
>process, you lo
Gilles Ganault a écrit :
So it looks like, unlike PHP, the prefered solution in Python is to
build a complete application as a long-running process, and either use
its embedded web server or configure a stand-alone web server to act
as reverse proxy using either FastCGI or WSGI to connect the two
On Mon, 12 Apr 2010 05:37:54 -0700 (PDT), Luis M. González
wrote:
>You should first investigate the different python web frameworks,
>choose one and then use the deployment options supported by your
>choice. These frameworks support several ways to deploy your apps,
>such as those you mentioned.
Gilles Ganault, 12.04.2010 11:57:
I'd like to make sure I understand what the options are to write web
applications in Python:
- à la PHP, using Apache's mod_python
- using eg. Lighttpd and configuring it to load the Python interpreter
every time a Python script is called (www.jakehilton.com/?q
On 12 abr, 06:57, Gilles Ganault wrote:
> Hello
>
> I'd like to make sure I understand what the options are to write web
> applications in Python:
>
> - à la PHP, using Apache's mod_python
>
> - using eg. Lighttpd and configuring it to load the Python interpreter
> every time a Python script is ca
On Mon, 12 Apr 2010 12:13:17 +0200, Daniel Fetchinson
wrote:
>For additional info have a look at http://wiki.python.org/moin/WebProgramming
Thanks for the link.
--
http://mail.python.org/mailman/listinfo/python-list
> I'd like to make sure I understand what the options are to write web
> applications in Python:
>
> - à la PHP, using Apache's mod_python
>
> - using eg. Lighttpd and configuring it to load the Python interpreter
> every time a Python script is called (www.jakehilton.com/?q=node/54)
>
> - long-run
Hello
I'd like to make sure I understand what the options are to write web
applications in Python:
- à la PHP, using Apache's mod_python
- using eg. Lighttpd and configuring it to load the Python interpreter
every time a Python script is called (www.jakehilton.com/?q=node/54)
- long-running pro
25 matches
Mail list logo
