Need to decide if Django is suitable for my application. I need to build a web application for 2-3 people. But they would each run their own copy on their local machine. It will effectively be like any regular app you download, install, and run. But it might become a shared web app in the future, so I'm building a web interface instead with a GUI interface.
The app is a specialized crawler. You import data from Excel. Then you fill out forms with options for the crawl. Then the app collects the data. This can take few minutes or hours, with some crawls lasting over a day (long story). Would Django be a good choice for this? Esp. compared to Cherrypy plus some other bits, or TurboGears, or Plyons, or something else. More specifically: 1. Is the builtin webserver sufficiently robust? My users do not want to install and configure apache. The builtin server is great, but will it be enough? I'm not concerned about performance and scalablity, just stability. The only feature I need is preventing access from other than the localhost. 2. Is sqlite fully supported? To simplify installation I would rather not have people install MySQL or PostgreSQL. It's overkill . But will I encounter any problems with sqlite? Any gotchas I should know about? 3. What about long-running processes? The importing and configuration is straightforward. But when you press "collect" it could churn for hours, some to the database, some to disk. Could Django handle such a long running queue? I could split the collection bit into a separate program. The web app would deal only with importing, configuring, and reviewing the data. 4. What about models not related to a table? The crawlers definition comes from a configuration file and associated classes. I don't want to tie the crawler config to a database. I want to modify the plaintext config file and then use this to generate the forms. I'm not quite clear how to create models in Django that are not connected to a database. Do I just do what I need to do in the views and the templates instead? Can someone point me to good examples about this? I have considered other options. Cherrypy is my strongest option depending on the answers to the above, and maybe some other things. Cherrypy + some other bits. Big attraction is that it has it's own, solid webserver. Big minus is that you need to add other bits which means more to learn for whoever takes over the project from me in a few months. Plus the documentation is not as helpful. It is flexible but you need to do a lot of stuff yourself. Turbogears. Could be good but in too much flux. Maybe in six months, but not now. Pylons. Ugh. Cobbles together too many things, which means reading piles of documentation and then interpreting each doc within the context of pylons. Plus, it is also in flux. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
