in reply to CGI vs Tk for application backend
Of course, I'm biased toward Tk, but there are advantages to using it, especially if it will only be run on 1 machine( i.e. no access needed thru the internet).
The main advantage is that you don't need to hassle with the programming ideosyncracies of the "stateless http protocol", like sending hidden fields, and storing sessions.
Tk will also give you a richer set of widgets to do your backend work. The html widgets are very limited, whereas as Tk will let you do just about anything you can dream up.
The Tk version "may" be more secure, since you are avoiding the unneccesary "apache middleman". If you have to setup a local apache server, for your workers, that can lead to complications....like firewall access, security issues, etc. Additionally, with Tk, you will be able to access more of the local filesystem and commands, without having to resort to using "sudo tricks".
So I would say, the only reason to use a browser interface, is if you want to remotely administer the store. But there too, Tk can access remotely thru encrypted connections.
Just as an example of the value of using Tk, just think about the problem of printing up shipping labels. I think it would be alot easier from a Tk script, than it would be thru a browser.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: CGI vs Tk for application backend
by Popcorn Dave (Abbot) on Oct 06, 2005 at 05:20 UTC |