> Pros: > - much more security, we can easily use industrial grade encryption and > passwords instead of relying on sketchy client browser habbits ( and > don't tell me the answer is to educate the clients, santa claus does not > exist anymore than my clients follow my instructions on browser use and > passwords )
No where exactly is SSL not industry strength? > - out of the browser css/dom hell for at least one side of the project Into the "the developer has to do it all by himself as nobody else can layout a gui-app"-hell, and creating that gui is by far more complex than writing some HTML templates. > - admin access can be locked down to specific machines ( I realize this > can be done with ip too but small business people tend not to want to > pay for a static ip for security purposes only ) I fail to see what that will buy you actually. > - testing and debugging would be easier Since when is testing gui apps easier? Au contraire, depending on your HTML things like selenium can help you tremendously, and the controller methods are easily tested. I'm not aware of a decent gui testing tool though. > - remote backups can happen without the user knowing, but on their > machines ( also possible in gears of course, but seems like it might be > easier What is a remote backup useful for exactly? I thought you want to use a DB. Which of course could need a backup... > Cons: > - have to install the app on the machines they will use, if they change > machines we need to reinstall, this could be a pain > - they can't change their minds and use a browser from a cafe > - maybe this is hard? I don't know ... I haven't tried making a desktop > app use sqlalchemy on a remote db yet. SA doesn't add anything to the complexity of GUI development - but depending on your toolkit there might be sql-aware widgets that directly bind to database tables, so you don't need SA there - but I personally prefer to use a "real" model anyway. > Unknown: > - is making forms and validation easier or harder? About the same I presume, depending on your toolkit. > - will it be faster and easier to handle persistence on the client end? No. And it will be harder IMHO, as GUI apps lack the "natural" request/response cycle that will act as good border for transactions. But on GUI apps, people expect undo and the like, and this makes things acutally more complicated. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
