I may be posting this question prematurely as I have not yet tried to implement my own instance of django running on apache or lighttpd but off-hand it seems that whenever I have a new application to launch, I am going to have to run a new fcgi daemon...is this accurate?
I am trying to integrate django into my University web. I see django as the perfect solution to optimize the tasks that clearly should be dynamic but have not yet been implemented to some web scripting language. I think part of my problem may be that I am approaching the implementation of django as I would the implementation of php. With PHP, I would throw a php script in a department's folder (thier 'site') which would handle all of their dynamic stuff. I can't see making a new fcgi daemon startup for every department that needs some dynamic content. While writing this post I realized that my solution may be making an app that is more or less a cms. I prefer to think of each dynamic need having its own seperate solution but it may just be that I write one app that manages many different disconnected webpages. Agh, I suppose I just need to rethink the way websites can be delivered, handled and managed. Question remains, one fcgi daemon per application? Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
