Issues of state (was: Tkinter or wxpython?)
- From: claird@xxxxxxxxx (Cameron Laird)
- Date: Tue, 7 Aug 2007 13:43:12 +0000
In article <mailman.1684.1186422197.22759.python-list@xxxxxxxxxx>,
Chris Mellon <arkanes@xxxxxxxxx> wrote:
.
[scores of lines
of vigorous debate]
.
.
Moreover, if you *don't* need global access or zero-deployment.
(zero-deployment is always nice but most environments where you can
reasonably force a specific browser and version also have IT
infrastructure), then you should ask yourself if forcing your
application in the web app model (I haven't even touched on the whole
stateless HTTP being mapped to a stateful environment issue, or the
need to manage the local web server) actually buys you anything. I
.
.
Go ahead: touch on statefulness. I've been pondering the topic
lately, and wonder what's new on the subject. I find it plenty
difficult to cast this as anything but a big liability for the
Web app team.
.
- Follow-Ups:
- Re: Issues of state (was: Tkinter or wxpython?)
- From: Paul Rubin
- Re: Issues of state (was: Tkinter or wxpython?)
- References:
- Re: Tkinter or wxpython?
- From: Chris Mellon
- Re: Tkinter or wxpython?
- From: Paul Rubin
- Re: Tkinter or wxpython?
- From: Chris Mellon
- Re: Tkinter or wxpython?
- Prev by Date: Re: Tkinter or wxpython?
- Next by Date: Which GUI toolkit (was: Tkinter or wxpython?)
- Previous by thread: Re: Tkinter or wxpython?
- Next by thread: Re: Issues of state (was: Tkinter or wxpython?)
- Index(es):
Relevant Pages
|