Going from webscripting to server-client software.
Cameron Laird
claird at starbase.neosoft.com
Mon Jul 30 09:55:41 EDT 2001
More information about the Python-list mailing list
Mon Jul 30 09:55:41 EDT 2001
- Previous message (by thread): Going from webscripting to server-client software.
- Next message (by thread): Going from webscripting to server-client software.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <97ae44ee.0107262155.5abdb82 at posting.google.com>, Stephen <shriek at gmx.co.uk> wrote: . . . >Really, I'm trying to get away from a stateless, non-updated-in-realtime >web app to more of a client app, something that might have been created >in Delphi or VB in the past. Especially since it might give us the >flexibility to integrate with other applications, such as the membership >system and email apps. (The web just doesn't lend itself to building >look-ahead auto-complete fields for names, emails etc). . . . Your parenthetical comment ... well, yes, that *certainly* is true. People *do* use Delphi and VB plenty, even in the present. If you can make enough assumptions about your Web client (that Java is enabled, and/or that you're using Netscape and you are willing to indulge in tricky multipart programming, and/or ...), you can get enough state to be useful. A lot of people would say at that point that you might as well do client-server without Web weight. -- Cameron Laird <claird at NeoSoft.com> Business: http://www.Phaseit.net Personal: http://starbase.neosoft.com/~claird/home.html
- Previous message (by thread): Going from webscripting to server-client software.
- Next message (by thread): Going from webscripting to server-client software.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list